Re: Where are plug-in classpaths resolved?

2006-12-07 Thread Andrew Williams
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

Where are plug-in classpaths resolved?

2006-12-06 Thread Wendell Beckwith
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

Re: Where are plug-in classpaths resolved?

2006-12-06 Thread Brett Porter
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 07/12/2006, at 10:20 AM, Wendell Beckwith wrote: Can a dev comment on http://jira.codehaus.org/browse/MANTRUN-51 and/or

Re: Where are plug-in classpaths resolved?

2006-12-06 Thread Wendell Beckwith
Thanks Brett. I'll try digging through it later tonight. Wb On 12/6/06, Brett Porter [EMAIL PROTECTED] 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 07/12/2006, at 10:20 AM, Wendell

Re: Where are plug-in classpaths resolved?

2006-12-06 Thread Jason van Zyl
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