Hi Mark,
Thank you for your answer! :)
Then I have another question: when 2 different dependency versions are at
the same level in the dependency tree, which one wins? Because in my case,
I have version 2.0 and version 1.0.1 of commons-lang at the same level, and
1.0.1 wins.
The highest-win strategy would be interesting, I agree.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
Mark Hobson
<[EMAIL PROTECTED]
l.com> Pour
Maven Users List
08/11/2005 13:49 <users@maven.apache.org>
cc
Veuillez Objet
répondre à Re: [m2] How dependency versions
Maven Users List are resolved with transitivity?
<[EMAIL PROTECTED]
che.org>
Hi Fabrice,
mvn currently mediates dependency versions using a nearest-wins
strategy. This means that the dependency version specified highest in
the dependency tree (i.e. nearest to the project being built) is used.
As a side note, I really need the highest-wins strategy - any pointers
to open issues or code required?
Mark
On 08/11/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hi,
>
> Does anyone know how Maven resolves a version for a specific depedency
when
> this dependency comes with different versions due to transitivity?
>
> I have the following case: I'm developing a framework where I use
> commons-lang version 2.0, along with other libs that have commons-lang in
> their POM, but with a different version (1.0.1 most of the time). In my
> WAR, I end up with version 1.0.1 of commons-lang.
> I know that projects using my framework can handle that by using
dependency
> management. However, I would expect that version 2.0 of commons-lang
would
> be used as I specified it in the deps of the POM of my framework
(shouldn't
> that "override" the version 1.0.1 given by transitivity of other libs ?).
>
> Thanks for you answer !
>
> Best Regards / Cordialement,
> Fabrice BELLINGARD
> DINQ/DSIN/INSI/EATE/IDVS/AIDV
> (+33) (01 61) 45 15 91 - [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
