Take the JAR of the maven-resources-plugin, delete the file META-INF/maven/plugin.xml and run maven. You'll get this error:
java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [org.apache.maven.plugins:maven-resources-plugin] was not found.
Description
Take the JAR of the maven-resources-plugin, delete the file META-INF/maven/plugin.xml and run maven. You'll get this error:
java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin
[org.apache.maven.plugins:maven-resources-plugin] was not found.
Technically, this is correct but doesn't really help to locate the root cause of the problem. If maven can't read the plugin.xml file of a plugin, it should abort with an error during the XML parsing step instead of trying to use the plugin anyway.
Real world case: The plugin is downloaded via a proxy and the download aborts before the full file is transferred or the proxy returns a HTML file ("A virus was detected blahblah") instead of the JAR. This can lead to corrupt JARs in the repository which leads to the error above.
PS: Not sure if this is "Plugin API" or "Plugins and Lifecycle". Please feel free to move the error report to the right place.
Aaron Digulla - 14/Apr/08 08:50 AM Technically, this is correct but doesn't really help to locate the root cause of the problem. If maven can't read the plugin.xml file of a plugin, it should abort with an error during the XML parsing step instead of trying to use the plugin anyway.
Real world case: The plugin is downloaded via a proxy and the download aborts before the full file is transferred or the proxy returns a HTML file ("A virus was detected blahblah") instead of the JAR. This can lead to corrupt JARs in the repository which leads to the error above.
PS: Not sure if this is "Plugin API" or "Plugins and Lifecycle". Please feel free to move the error report to the right place.
Real world case: The plugin is downloaded via a proxy and the download aborts before the full file is transferred or the proxy returns a HTML file ("A virus was detected blahblah") instead of the JAR. This can lead to corrupt JARs in the repository which leads to the error above.
PS: Not sure if this is "Plugin API" or "Plugins and Lifecycle". Please feel free to move the error report to the right place.