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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.1.0
• Component/s: Plugins and Lifecycle
• Assignee: Benjamin Bentmann
• Reporter: Benjamin Bentmann
• Created: 15/Mar/09 07:41
• Updated: 15/Mar/09 09:27
• Resolved: 15/Mar/09 09:27

Description

Invoking

mvn org.apache.maven.plugins:maven-clean-plugin:LATEST:clean

dies with

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)

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