You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/03/12 19:21:13 UTC
[jira] Closed: (MNG-137) Transparent plugin downloading

     [ http://jira.codehaus.org/browse/MNG-137?page=history ]
     
Brett Porter closed MNG-137:
----------------------------

    Resolution: Fixed

this works as designed for now. improvements will be made in future releases

> Transparent plugin downloading
> ------------------------------
>
>          Key: MNG-137
>          URL: http://jira.codehaus.org/browse/MNG-137
>      Project: m2
>         Type: Task
>     Reporter: Jason van Zyl
>     Assignee: Jason van Zyl
>      Fix For: 1.0-alpha-1

>
>
> Before we start advocating people specify plugins as dependencies in their POMs I would like to discuss a simple approach that will scale to any number of plugins.
>                                                                                                                                                                                                       
> Ultimately, I believe the goal is to ease the burden for the user. To that end I think plugins being downloaded transparently when required is the ideal to strive for. Plugins have to be located outside the core and I believe it is entirely possible to make all plugins external to the core.
> By having a simple convention where the goal is prefixed by the name
> of the plugin that it belongs to. So something simple like:
> antlr:generate
> Would simply look for the antlr plugin. So we could also simplify the naming of the plugins as jar as packaging goes too and stop assuming maven-foo-plugin.
> To keep people from complaining about having to type foo:bar we can create a simple alias mechanism so people can make short cuts for themselves if they wish. But most of the time someone would check a build out and run the default goal, if anything special is required it should be automatically downloaded.
> This way the maven core can ship with the basic six plugins to build and test projects and everything above that gets downloaded, but transparently as not to burden the user.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira