Thanks for linking to the Jira Issue I created a few days ago. This traffic should raise some attention. It's an annoying problem for us that puts our build validity at risk. The Maven-Jenkins integration is a great feature for us.
https://issues.jenkins-ci.org/browse/JENKINS-15367 Kohsuke Kawaguchi is now assigned (by himself). It might help for you to add comments to the Jira with any details you've noticed. On Wednesday, September 19, 2012 10:04:37 AM UTC-5, Larry Shatzer, Jr. wrote: > > I've noticed something weird with Maven projects that are set to build > downstream jobs if there is a SNAPSHOT dependency. It now lists jobs as > dependencies (and builds them) even if it is not a SNAPSHOT dependency but > a regular dependency. > > It looks like the code for JENKINS-12735 to allow version ranges is > causing this. If you use version of <version>1.0.0</version>, that should > not trigger it, but the other uses like [1.0.0,2.0.0), etc. should. This is > causing lots of extra unnecessary builds when you have a lot of projects > that are dependent on each other, but set to a release of the other and not > a SNAPSHOT. > > -- Larry >
