On 19-Feb-08, at 9:46 AM, Carlos Sanchez wrote:
On Feb 19, 2008 9:40 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 19-Feb-08, at 9:36 AM, Carlos Sanchez wrote:
I think you misunderstood. The dependencyManagement is used for
project dependencies, fine with that.
When you use a plugin no dependencyManagement is applied. The
current
project depMan shouldn't be applied because it's only for
projects, so
that's ok.
The problem comes when a plugin is built using
dependencyManagement to
force some dependencies. When that plugin is used, the
dependencyManagement of the plugin is ignored, so you run it with
different dependencies than the ones you build it with.
So there is no Map used during the plugin's artifact resolution at
runtime is what you're saying, yes?
right, and I think it should use the plugin Map that was used during
the plugin build
That should happen as a natural consequence of using a Map with
artifact resolution. Which I see is in the patch and I agree that's
what should happen.
Just trying to think of who that might hose changing that one line.
People might be getting things from something in their project by
proximity who will now get it from the plugin. It's definitely fine in
trunk, do we want to to that in the branch though?
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
Selfish deeds are the shortest path to self destruction.
-- The Seven Samuari, Akira Kirosawa
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
