After updating my jenkins server to version 1.481, the maven dependencies (version-number) will not be resolved correctly anymore. Let me give you an example to explain the problem in detail:
I have two projects “BASE” and “DELTA”. Both projects are hosted on a svn-repository. Project DELTA exists only in trunk, project BASE in trunk (ver. 0.2.0-SNAPSHOT) and in a branch (ver. 0.1.3-SNAPSHOT). The DELTA-branch has a dependency on an stable BASE-version (ver. 0.2.2, which can be found on a nexus repository), DELTA-trunk depends on BASE-SNAPSHOT version. On Jenkins I created three “maven2/3 projects” (BASE, DELTA and DELTA-branch). I set up the configuration for every project in the same way: checked the options “Build whenever a SNAPSHOT dependency is built”, “Poll SCM” on “Build Triggers” and checked “Resolve Dependencies during Pom parsing” in the “Build”-section.
When I commit sources of the BASE-Project, Jenkins will built the BASE-job. After finishing, he will start both DELTA-jobs without checking the version-number of the dependency. I would expect that Jenkins would only built the DELTA-trunk project like the older version of Jenkins (ver.1.438). Can you tell me anything that has changed with the new version that my caused this problem or give me a solution for my problem?