-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
I am using Hudson version 1.255.
Given the following jobs:
MasterA job has a pom.xml (parent with 2 modules)
- projectOne module has a pom.xml that creates one-1.0.0.jar (has MasterA as
parent) - projectTwo module has a pom.xml that creates two-1.0.0.jar (has MasterA as
parent)
MasterB job has a pom.xml (parent with 1 module)
- projectThree module has a pom.xml that creates three-1.0.0.jar (has MasterB
as parent and has a dependency on one-1.0.0.jar)
If I make a code change to MasterA's projectOne, it correctly triggers a
downstream build of job MasterB.
However, if I make a code change in MasterA's projectOne and increase the
version so that one-2.0.0.jar gets createdd, then MasterB's job is still
triggered for a build even though it still uses one-1.0.0.jar.