I'm using Hudson on Windows and Clearcase as SCM.

My maven2 project has a aggregation pom in the root of the Clearcase Vob and several module poms in the folder beneath this root folder.
When I setup a job to do continuous integration I've set the flag to true for the "Incremental build" option.
I've then made a trigger in Clearcase to trigger the build when a user checks in an element.
The trigger is nicely cached in Hudson and the job is started. The maven goals are "clean install".

So far, so good. Until Hudson has to decide what module it should build. Or, in other words, what file was checked in in what module. Suppose one has 2 modules. Then if a file is checked in in the first module, only this module and all dependent modules should be build.

In the log, I can see that the function "cleartool lshistory" is started and that the checked-in file is detected. Also the changelog.xml in the job folder has a reference to this file.

After the lshistory has run and the view is updated (if it is a snaphot view), a java program is started with as argument hudson.maven.agent.Main and a few extra arguments and a classpath spec. I suppose this is the program that defines the specific pom of the module that the checked in file includes.

But, and now it comes, no matter what file I check in, the maven command line has the root pom as argument after the -pl maven option. (if a incremental build is selected and detected, the maven parameters are changed to "-amd -pl").

What could be the fault? May be I've overlooked something.
If we can not build a "incremental build" then continiuous integration doesn't work at all.

The current version I use is 1.368 but I have even updated to the latest Hudson version but the results were the same.