You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/10/03 04:38:09 UTC

[jira] Updated: (MNG-611) improve independence of plugins from core

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

Brett Porter updated MNG-611:
-----------------------------

    Fix Version:     (was: 2.0-beta-3)
                 2.1

did some work on this, but we can look to improve it in future.

> improve independence of plugins from core
> -----------------------------------------
>
>          Key: MNG-611
>          URL: http://jira.codehaus.org/browse/MNG-611
>      Project: Maven 2
>         Type: Task
>   Components: maven-plugins
>     Reporter: Brett Porter
>      Fix For: 2.1

>
>
> currently, the coupling of the plugins is often very tightly related to the core, which can cause a problem if the API changes and the plugins are to be used across versions.
> we should look to:
> 1) separate the classloaders as much as possible (see other issue)
> 2) try and minimise and stabilise the public API of those being used (artifact, project, plugin-api most notably)
> 3) reduce use of Maven dependencies where possible
> 4) look at the expressions available and see if too much is exposed

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org