![]() |
|
|
|
|
Change By:
|
Jesse Glick
(23/Jan/13 10:01 PM)
|
|
Description:
|
In 1.480 I encountered an unreproducible exception:
{code:none}
java.lang.NoClassDefFoundError: org/apache/maven/plugin/MojoExecution
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2442)
at java.lang.Class.privateGetPublicMethods(Class.java:2562)
at java.lang.Class.getMethods(Class.java:1427)
at org.kohsuke.stapler.ClassDescriptor.<init>(ClassDescriptor.java:73)
at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:96)
at org.kohsuke.stapler.MetaClass.<init>(MetaClass.java:84)
at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:182)
at org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:104)
at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:164)
at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:151)
at hudson.Functions.hasView(Functions.java:1078)
…
at jenkins.model.GlobalPluginConfiguration.config.run(config.groovy:8)
{code}
Something wrong the Maven plugin, presumably. Yet the error recovery was poor: the {{/configure}} screen displayed the exception but failed to complete loading.
# {{Functions.hasView}} should catch various errors and just return {
[
{
false}}.
# {{MetaClass}} should probably annotate linkage errors with the starting class, for diagnosis.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
