In our environment, we have few dedicated maven configuration files, one
settings.xml per environement. These files are neither located in the
%MAVEN_HOME%\conf nor in the %USERPROFILE%\.m2

While configuring projects in Hudson, I have noticed the following problem: for
"Maven 2 project" configuration, while specifying an alternate settings.xml
path, (using -s option), the build is in failure. The -s option is not
interpreted by the build.

If I use the same command with a "free style" project configuration, the build
is successful. The behavior is equivalent to the maven command line behavior.

Is this behavior for "Maven 2 project" already known to the Hudson community? Is
there

• any planned fix or
• a workaround different from using the freestyle configuration

Regards,

jean-michel legrand