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/08/28 15:44:03 UTC

[jira] Reopened: (MNG-449) plugin development without release use case

     [ http://jira.codehaus.org/browse/MNG-449?page=all ]
     
Brett Porter reopened MNG-449:
------------------------------

     Assign To:     (was: John Casey)

this is really annoying. we need to make it such that any invocation of "m2 install" makes that plugin the default

> plugin development without release use case
> -------------------------------------------
>
>          Key: MNG-449
>          URL: http://jira.codehaus.org/browse/MNG-449
>      Project: Maven 2
>         Type: Bug
>   Components: maven-artifact
>     Versions: 2.0-alpha-2
>     Reporter: Brett Porter
>      Fix For: 2.0-beta-2

>
>
> currently, a plugin used from the command line or a POM without a version uses the latest release. This is inconvenient and confusing when you are developing a plugin as you need to do the first install with -DupdateReleaseInfo to get it to use your version.
> There needs to be a better way to do this. It may be solved by existing issues relating to the RELEASE and plugin version management. If not, then another alternative might need to be considered, like local installation triggering a RELEASE update.

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