[regression] Explicitly using plugin metaversions crashes plugin manager
------------------------------------------------------------------------

                 Key: MNG-4086
                 URL: http://jira.codehaus.org/browse/MNG-4086
             Project: Maven 2
          Issue Type: Bug
          Components: Plugins and Lifecycle
    Affects Versions: 2.1.0
            Reporter: Benjamin Bentmann


Invoking
{noformat}
mvn org.apache.maven.plugins:maven-clean-plugin:LATEST:clean
{noformat}
dies with
{noformat}
java.lang.IllegalStateException: The plugin descriptor for the plugin Plugin 
[org.apache.maven.plugins:maven-clean-plugin] was not found.
Please verify that the plugin JAR 
U:\Jeder\Maven-2\org\apache\maven\plugins\maven-clean-plugin\2.3\maven-clean-plugin-2.3.jar
 is intact.
        at 
org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:328)
        at 
org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:213)
        at 
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:175)
{noformat}

While users usually won't need to explicitly use RELEASE or LATEST, plugin 
developers do occasionally for testing.

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

        

Reply via email to