I'm concerned by this "fix" too. Here are my thought for now: the fix should not have been done in VersionRange but in a version conflict resolution phase, since a range is a mathematical notion we can't alter.
but I didn't have time yet to transform these thoughts in code... Regards, Hervé Le vendredi 03 septembre 2010, Brian Fox a écrit : > Forking this discussion: > > On Thu, Sep 2, 2010 at 9:12 PM, Mark Derricutt <m...@talios.com> wrote: > > 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. > > Not possible for 3.0 > > > 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". > > Seems logical to me, not sure how much work that is to fix, but > patches would be a good way to ensure this gets in. Certainly I could > see this being a problem that's worth trying to address prior to M3.0 > if it's not risky. > > > 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. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
