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-alpha-3
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
