You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2006/06/22 22:52:40 UTC

[jira] Updated: (MNG-2014) build extension libraries should be added to the current artifact filter used by the plugin manager

     [ http://jira.codehaus.org/browse/MNG-2014?page=all ]

John Casey updated MNG-2014:
----------------------------

    Fix Version:     (was: 2.0.5)
                 2.1

flexible artifact filter in the core classloader falls under the heading of customizing a maven instance, which is a topic we're trying to design/implement for 2.1.

> build extension libraries should be added to the current artifact filter used by the plugin manager
> ---------------------------------------------------------------------------------------------------
>
>          Key: MNG-2014
>          URL: http://jira.codehaus.org/browse/MNG-2014
>      Project: Maven 2
>         Type: Bug

>   Components: Plugins and Lifecycle
>     Versions: 2.0.2
>     Reporter: John Casey
>      Fix For: 2.1

>
>
> currently, build extensions are not added to the artifact filter that the plugin manager uses when initializing plugin containers. This means that plugins will get another copy of any class in that build extension.
> Build extensions go into the core container, and should therefore be excluded from plugin containers, to ensure that plugins and the core can share the classes/instances in the extension.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira