On 19-Feb-08, at 9:07 AM, Carlos Sanchez wrote:
On Feb 19, 2008 7:46 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
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.
it is, the problem is dependencyManagement in the plugin pom
Then somewhere the Map that is used for managed dependencies is
getting fed into both the project's resolution and the plugin's
resolution and that definitely needs to be separated. Even if we
decide there are certain cases where they should be shared (and I
can't actually think of any real cases except for maybe Antlr vX
generated code needing Antlr vX runtime code which needs to be
aligned) they should be separate so we knowingly combine them if
necessary.
Problem is if you find that shared Map what are we going to break if
you separate them now? Just thinking aloud.
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?
dependencyManagement in plugin's pom (A)
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]
--
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
----------------------------------------------------------
First, the taking in of scattered particulars under one Idea,
so that everyone understands what is being talked about ... Second,
the separation of the Idea into parts, by dividing it at the joints,
as nature directs, not breaking any limb in half as a bad carver might.
-- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
