Yup, these changes are in trunk now :)
Andy
Jason van Zyl wrote:
On 6 Dec 06, at 8:18 PM 6 Dec 06, Brett Porter wrote:
DefaultPluginManager is the place to look. You are looking for the
creation of a child plexus container, and jar resources being added
to that.
On the code we're about to merge into trunk the container creation is
now gone. It's the same place in the DefaultPluginManager but we are
now creating a Realm per component which is a Realm per plugin (maven
plugin = plexus component). So there is no multiple container creation
per run of Maven. This code is about to be merged to trunk if it is
not already.
Jason.
On 07/12/2006, at 10:20 AM, Wendell Beckwith wrote:
Can a dev comment on http://jira.codehaus.org/browse/MANTRUN-51 and/or
http://jira.codehaus.org/browse/MANTRUN-63 since I'm pretty sure
their one
and the same? This is such an issue to work around that previously
I got
around it by breaking my command invocation into 2 separate mvn
invocations
through our build server, but now I want to conditionally activate a
profile
and this bug negates that capability. I realize people are busy but
if I
can be pointed to the code location(s) that resolves plug-in
classpaths then
I can see about creating a patch.
Wb
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]