maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Derricutt <m...@talios.com>
Subject Re: Alternative dependency mediation
Date Sat, 04 Jun 2011 11:57:17 GMT
Would be nice if this was pluggable.  We've (me and others out the Illegal
Argument podcast) lamented Maven not resolving the "lowest version in the
range" when compiling.


-- 
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree


On Wed, Jun 1, 2011 at 9:28 PM, Leonard Ehrenfried <
leonard.ehrenfried@web.de> wrote:

> 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 <anders@hammar.net> 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 <sshock@gmail.com>
> 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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message