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

["John Casey (JIRA)" <ji...@codehaus.org>]

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

John Casey updated MNG-449:
---------------------------

    Remaining Estimate: 3 hours
     Original Estimate: 10800

need to write a new mojo for the plugin-plugin to update the version in the plugin registry when a plugin is installed...also, need to workup an IT to specifically test -cpl AND --check-plugin-latest.

> 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
>     Assignee: John Casey
>      Fix For: 2.0-beta-3

>
> Original Estimate: 3 hours
>         Remaining: 3 hours
>
> 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