On 5/4/06, Feniks Nator <[EMAIL PROTECTED]> wrote:
This in discussed in the book Better Builds with Maven which you find here
(for free):
http://www.mergere.com/m2book_download.jsp
See the following sections:
p54: 3.4 Managing Dependencies
p.57: 3.6 Resolving dependency conflicts....
I think those solutions are rather good.
The one thing that relates to what I am facing is the following:
"The version selected is the nearest to the top of the tree. [...] A
dependency in the POM being built will be used over anything else".
(3.6)
I don't really see why maven must take a decision, but I probably
don't have the full overview of the issues. Sub projects should work
on their own as well as when grouped, otherwise that makes aggregating
projects together a potential source of failure.
If I have P2 a sub module of P1, m2 could run P1 according to what is
defined in P1's pom, but P2 according to what is defined in P2's pom.
A user dependency version override should have a bigger precedence
over what is derived from the tool's implicit setup.
Anyway my issue's fixed and I know why it works like that, even though
I find it strange. Seems that I read that part of the book too fast.
Thanks for pointing me to the paragraphes.
Jerome
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
