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. On 5/4/06, jerome lacoste <[EMAIL PROTECTED]> wrote:
Hi. if I have P1 |- P2 Now P2 requires a particular version of a plugin, newer than the one taken by default by P1. After changing P2's pom, if I build from P2, then my P2 build will work. But if I build from P1, P2 will fail. My solution was to move the plugin-version specification in the root pom, but I found that counter intuitive. Comments? Jerome --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
