Hey all, A while I posted on a change in version range behaviour under Maven 3 (MNG-3092 [1]) but didn't really get much response ( which may have unfortunately been related to my tone at the time ).
Any way, the change in question is that version ranges no longer resolve a -SNAPSHOT version unless that range includes the -SNAPSHOT as either the upper or lower bound. In general I think this is an awesome change as it solves a lot of issues, and will help prevent accidental API breakages. However, it also breaks the way our projects are setup for integration testing and packaging - and if this change does remain in Maven 3 final, I was hoping to find a way to work around/adapt our builds. Currently, we set out inter-project dependencies on a range of [2.0.0,3.0.0) - meaning anything in the 2-series gets picked up. Under Maven 3 this falls down for our integration test project which we want to pick up any -SNAPSHOT version in the range so that any problems are picked up BEFORE releasing individual artifacts. This also falls down for our distribution builds, where for a SNAPSHOT distribution, we'd want them. Ideally, what I'd love to see is a way of allowing -SNAPSHOT resolution in ranges as an option, so that for those particular artifacts that need it, still get them. Thoughts? Mark [1] http://jira.codehaus.org/browse/MNG-3092 -- Pull me down under...
