How do you keep Hudson from giving Maven the -B option to build?

Question

When Hudson is about to build my project, he runs Maven as follows:

Executing Maven:  -B -f /path/to/root/pom.xml clean install

This works great for most projects. (-B for batch or non-interactive mode, BTW).

But for this one project that uses AndroMDA (which I cannot recommend for future projects, it really hurts the-butt, slows down the build by 1000% with code generation for things that could be done trivially with inheritance and annotation-based configuration).

For some reason unknown to me when the -B flag is assigned to Maven, the generated classes do not fit into the class path, causing compilation errors for references to the generated classes. I tested the creation manually with and without -B, and the result is that it builds fine without -B (outside of Hudson), and it doesn't build with -B (again, outside of Hudson).

Using Hudson version 1.369 and Maven 2.2.1 external installation.

Any advice is greatly appreciated !!!

PS Hudson AMAZING !!!!

Answer 1

The simplest version should be to have a free style project and call maven yourself.