Personally I'd still like to see some resolution to the problems introduced by the version range resolution change ( no more -SNAPSHOT resolution except for on the bounds ).
On one hand I applaud the change from a release standpoint, but it currently causes issues for our integration build processes. Two options come to mind: 1) Explicit GAV patterns for -SNAPSHOT resolution get defined somewhere 2) If a GAV is a particpant in a reactor build, it's -SNAPSHOT should be considered kosher for resolution Option 1 would probably require some form of POM change as I don't think the resolution part of a configurable plugin, so most likely can't be done. Option 2 should be fine, as when releasing an individual artifact, nothing external would be in the reactor, unless it was part of the build chain, so no extraneous -SNAPSHOTs would be considered. This should give a fairly good compromise between "fixing ranges for release" and "not breaking existing builds". Each time I've brought the subject up I don't seem to see any traction or replies/discussion come along, is there room to address this somehow? -- Pull me down under... On Fri, Sep 3, 2010 at 11:34 AM, Brian Fox <bri...@infinity.nu> wrote: > Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty > safely call it feature complete. I'd like to propose a few goals to > get some things done. We have ApacheCon coming up the first week of > November, and it would be great to set that as a target to get Maven > 3.0 out the door. >
