[
http://jira.codehaus.org/browse/MNG-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130742#action_130742
]
Aaron Digulla commented on MNG-3523:
------------------------------------
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.
> Bad error message if plugin.xml is missing/corrupt
> --------------------------------------------------
>
> Key: MNG-3523
> URL: http://jira.codehaus.org/browse/MNG-3523
> Project: Maven 2
> Issue Type: Bug
> Components: Plugin API
> Affects Versions: 2.0.9
> Reporter: Aaron Digulla
>
> 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.
--
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
