[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Thank you! 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
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Agreed, the error is really not informative... 3.21 worked for a project that had the warnings post-build action already configured, but I've since removed it so I can't try to a build out to see. However, with 3.21 in my 1.474 installation, it now allows me to add "Scan compiler warnings" as a post-build action, but when I press "Add" to add a new parser, nothing happens, and nothing appears in the log. This is an elusive bug! I'm going to try a bunch of different versions of the plugin to see if I can get any of them working. 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
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Oh, perhaps this is a bit more helpful of an error message. I installed 4.12 and now get this in the log when trying to add a post-build action (relevant lines only): WARNING: Caught exception evaluating: action.iconFileName!=null. Reason: java.lang.reflect.InvocationTargetException ... Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file ... at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at hudson.plugins.warnings.WarningsResultAction.getSmallImage(WarningsResultAction.java:63) at hudson.plugins.analysis.core.AbstractResultAction.getIconFileName(AbstractResultAction.java:138) 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
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? analysis-core is version 1.43, yeah. 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
[JIRA] (JENKINS-14461) Warnings plugin no Java 1.5 compatible?
Trevor Bekolay created JENKINS-14461 Warnings plugin no Java 1.5 compatible? Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 17/Jul/12 1:38 PM Description: After upgrading Jenkins and Warnings, my projects no longer showed up. System log was pointing to the Warnings plugin, so I disabled it and they came back. I disabled the post-build trigger and reeanbled Warnings, which didn't cause a problem. However, when I tried to re-add the console output as a post-build step, nothing happens. Looking at the log, I get this output: WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: file:/srv/hudson/plugins/warnings/WEB-INF/classes/hudson/plugins/warnings/WarningsPublisher/config.jelly:4:124: j:invokeStatic Bad version number in .class file at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:735) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:290) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at hudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:91) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:104) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:62) at org.kohsuke.stapler.Function.renderResponse(Function.java:103) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:92) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:439) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:125) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay updated JENKINS-14461 Warnings plugin not Java 1.5 compatible? Change By: Trevor Bekolay (17/Jul/12 1:42 PM) Summary: Warningsplugin no not Java1.5compatible? 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
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? I updated to 4.11 (the latest at http://updates.jenkins-ci.org/download/plugins/warnings/ ) and am still having the same issue. The start of the stack trace (not sure if the rest is useful?): 17-Jul-2012 9:35:01 AM hudson.widgets.RenderOnDemandClosure$1 generateResponse WARNING: Failed to evaluate the template closure org.apache.commons.jelly.JellyTagException: file:/srv/hudson/plugins/warnings/WEB-INF/classes/hudson/plugins/warnings/WarningsPublisher/config.jelly:4:124: j:invokeStatic Bad version number in .class file 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
[JIRA] (JENKINS-14461) Warnings plugin not Java 1.5 compatible?
Trevor Bekolay commented on JENKINS-14461 Warnings plugin not Java 1.5 compatible? Okay, I installed the most recent LTS (1.447.2). Now, I am not getting any errors in the log, but projects cannot be configured. If I try to configure a project, it continues to display the LOADING text with grey overlay; scrolling down, the post-build actions are loaded up until the Warnings plugin, it seems. But, as I said, nothing shows up in the log. This is with the updated 4.11 plugin. It might be worth mentioning that the previously installed version, before upgrading to 4.10, was 3.21, and it worked perfectly then. 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
