On 18-Feb-08, at 11:54 PM, Carlos Sanchez wrote:
I'd like to get some feedback in MNG-3410, particularly from John as
he has been working on this.
If you build and install a plugin with managed versions that affect
plugin transitive dependencies, when it's used the dependency
management is ignored
If the dependency management affects the plugin direct dependecies it
works properly because the information is merged.
Dependency management should not affect anything to do with plugins.
If that is happening that is completely wrong.
Dependencies and what plugins use should be completely separate. A
project's classpath should never affect what is used in a plugin's
execution.
eg.
Plugin A depends on jar B that depends on jar C[1.0]
A dependencyManagement explicitly forces C[2.0], you build and install
using C[2.0] in the classpath
dependencyManagement in your POM or in the plugin's POM?
If you use plugin A in your pom it will be used with C version 1.0
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
A language that doesn’t affect the way you think about programming is
not worth knowing.
-— Alan Perlis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
