On 19-Feb-08, at 9:56 AM, Niall Pemberton wrote:
On Feb 19, 2008 5:46 PM, Carlos Sanchez <[EMAIL PROTECTED]> 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
Perhaps related, but I tried specifying a later version of a plugin's
dependency and it was ignored:
See http://maven.markmail.org/message/km5mlcfsgqlo7le2
The ordering that should happen is the Map should align everything
within the plugin, which it currently isn't and then the user
specified plugin dependencies should be obeyed. This works in trunk,
so if this doesn't work in 2.0.x that's a bug. Users should be allowed
to override the version of a tool bundled with said plugin.
Niall
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
