We tried to change the version *range* resolution strategy once at my old company. We found that this component is not injected by the DI container but rather instantiated with 'new'.
A colleague of mine wrote a patch and opened a ticket [1] that does exactly that. We didn't end up using the patch ourselves but maybe it can give you a clue where you need to be looking. [1] http://jira.codehaus.org/browse/MNG-5017 Lenni On Wed, Jun 1, 2011 at 6:39 AM, Anders Hammar <[email protected]> wrote: > No, it doesn't. At least not out-of-the-box. I don't know if it would be > possible to extend in any way to get this behavior. > > /Anders > > On Wed, Jun 1, 2011 at 06:08, Phillip Hellewell <[email protected]> wrote: > > > Does Maven 3.x support any strategies other than "nearest definition" for > > transitive dependency mediation? > > > > Specifically I am interested in if it has the ability to use the "highest > > version #" found anywhere in the dependency tree. > > > > Phillip > > >
