Why does Hudson ignore my profiles.xml file?
I have a Maven2 project, with a pom.xml and a profiles.xml files at the same level.
The project configuration is provided by Maven profile properties:

    dbhost=${dbhost}
    dbport=${dbport}
    // etc.

Locally, each developper customize his build in the "profiles.xml". It works well.

For continuous integration, a ci "profiles.xml" has been put on our SCM server (at the same level as the pom.xml).

The problem is that Hudson simply ignores this file during the Maven build, whereas the "-P hudsonprofile" is correctly set.

If the same profile is moved directly in the "pom.xml", or in the global "settings.xml" the build works. So we already have a solution.

I also know that the "profiles.xml" file is deprecated, but I would like to understand why the comportement is different between Hudson build and my local build...

Note: Hudson and my local build use the same version of Maven (2.2.1).
Why does Hudson ignore my profiles.xml file?
===

I have a Maven2 project, with a pom.xml and a profiles.xml files at the same level.
The project configuration is provided by Maven profile properties:

    dbhost=${dbhost}
    dbport=${dbport}
    // etc.

Locally, each developper customize his build in the "profiles.xml". It works well.

For continuous integration, a ci "profiles.xml" has been put on our SCM server (at the same level as the pom.xml).

The problem is that Hudson simply ignores this file during the Maven build, whereas the "-P hudsonprofile" is correctly set.

If the same profile is moved directly in the "pom.xml", or in the global "settings.xml" the build works. So we already have a solution.

I also know that the "profiles.xml" file is deprecated, but I would like to understand why the comportement is different between Hudson build and my local build...

Note: Hudson and my local build use the same version of Maven (2.2.1).