I'd had a similar thought initially, but I've not really looked at the internals of maven yet to know if there is such a distinct thing, or a pluggable resolver ( I did see that the resolution was on the VersionRange class so I suspect maybe there isn't ).
Mark -- Pull me down under... On Fri, Sep 3, 2010 at 5:40 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > 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. >
