Hi There,

I'm not sure if this is known, but I haven't been able to find this particular
issue via web searches or looking through the issue tracker.

Our particular issue is that we are building CVS and Clearcase artifacts using
maven from within Hudson.

For the CVS artifacts, when an artifact is built the snapshot dependency
resolution code runs perfectly and triggers builds for the artifacts that have a
dependency on what was just built.

For any of our Clearcase artifacts, regardless of whether it should have been
triggered from a CVS build, or another Clearcase build the dependency resolution
code doesn't seem to run.

As far as output logs for a build go, all I see is the Parsing POMs message,
then it runs into the build without mentioning anything else it has found.
This is unlike CVS builds, which always have a "Discovered a new module x.x.x:xx
Blah" kind of message

The only thing I can think of which could affect how the dependency resolution
works is our build jobs for CVS check out the CVS code directly into the build
job on the slave, whereas the Clearcase job creates a view within the directory
for the build job on the slave.

This results in the following file structures.

CVS:

build_x
<files>
pom.xml

Clearcase:

build_x
XX_IOS_BusCom_CI
IOS
view.dat
IOS_BUSCOM
ios-business-common
<files>
pom.xml

As you can see, the directory structures are vastly different, and I think this
is what is causing the dependency resolution section to fail.

If there is a simple fix for this problem that would be great, but if not, I
think either being able to specify where the pom file for each build project is
to be parsed, or to make the dependency resolution code robust enough to try
find a pom.xml in every build project there is in the workspace.

If there's any other information I can provide I will do so as best I can.

We are currently using Hudson ver 1.290, Clearcase Plugin ver 0.8.1.