[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros updated an issue Jenkins / JENKINS-54959 Offer a new Unarchive installer which takes Java archive structure into account Change By: Bruno Medeiros Comment: It seems that setting the "Subdirectory of extracted archive" of the JDK tool configuration is a valid workaround:!screenshot-1.png|width=485,height=177,thumbnail! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195983.1543566344000.7223.1564825200816%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros commented on JENKINS-54959 Re: Offer a new Unarchive installer which takes Java archive structure into account It seems that setting the "Subdirectory of extracted archive" of the JDK tool configuration is a valid workaround: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195983.1543566344000.7218.1564825140160%40Atlassian.JIRA.
[JIRA] (JENKINS-54959) Offer a new Unarchive installer which takes Java archive structure into account
Title: Message Title Bruno Medeiros updated an issue Jenkins / JENKINS-54959 Offer a new Unarchive installer which takes Java archive structure into account Change By: Bruno Medeiros Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195983.1543566344000.7213.1564825020409%40Atlassian.JIRA.
[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)
Title: Message Title Bruno Medeiros commented on JENKINS-55668 Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2) Same problem for OpenID Connect support: JENKINS-55668 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55668) Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2)
Title: Message Title Bruno Medeiros edited a comment on JENKINS-55668 Re: Unable to login with Bitbucket Oauth plugin after Jenkins update (2.150.2) Same problem for OpenID Connect support: JENKINS- 55668 55669 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55669) Auth plugin doesn't work after upgrade to Jenkins 2.150.2
Title: Message Title Bruno Medeiros updated an issue Jenkins / JENKINS-55669 Auth plugin doesn't work after upgrade to Jenkins 2.150.2 Change By: Bruno Medeiros Keycloak plugin is broken after 2.150.2 update, as described here is this other OpenID Connect plugin:[https://github.com/jenkinsci/oic-auth-plugin/issues/54] Also seems related to:https://issues.jenkins-ci.org/browse/JENKINS-55668 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55669) Auth plugin doesn't work after upgrade to Jenkins 2.150.2
Title: Message Title Bruno Medeiros created an issue Jenkins / JENKINS-55669 Auth plugin doesn't work after upgrade to Jenkins 2.150.2 Issue Type: Bug Assignee: D. Lauer Components: keycloak-plugin Created: 2019-01-18 04:19 Priority: Blocker Reporter: Bruno Medeiros Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51549) Infinite Loop - Keycloak Plugin
Title: Message Title Bruno Medeiros edited a comment on JENKINS-51549 Re: Infinite Loop - Keycloak Plugin I know this is not a forum, but this issue is very high highly ranked on Google if you get infinite loops. .. so: In my case they were initially being caused by a misconfiguration in SSL certificates of the IdP, the server had some missing intermediate certificates.After that, another problem with the clock of the client machine, causing valid tickets to be interpreted as expired ones. After fixing these two issues, everything is working greatly :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51549) Infinite Loop - Keycloak Plugin
Title: Message Title Bruno Medeiros commented on JENKINS-51549 Re: Infinite Loop - Keycloak Plugin I know this is not a forum, but this issue is very high ranked on Google if you get infinite loops. In my case they were initially being caused by a misconfiguration in SSL certificates of the IdP, the server had some missing intermediate certificates. After that, another problem with the clock of the client machine, causing valid tickets to be interpreted as expired ones. After fixing these two issues, everything is working greatly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sonar] (JENKINS-18600) Can't send new jobs to Sonar after Sonar upgrade: Not authorized
Bruno Medeiros commented on JENKINS-18600 Cant send new jobs to Sonar after Sonar upgrade: Not authorized I had a similar problem, and it was a Sonar fault. My Sonar has a LDAP auth, and one non-LDAP user for Jenkins. At some Sonar upgrade, the non-LDAP user stopped working together with LDAP users, it gives me always auth error, that was why Jenkins Sonar Plugin also stopped working. If that is the case, you need to use sonar.security.localUsers, see http://sonarqube.15.x6.nabble.com/cannot-login-to-sonar-using-created-user-and-ldap-td5025428.html and http://jira.codehaus.org/browse/SONAR-4543. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21712) Jenkins Update breaks Subversion credential configuration
Bruno Medeiros commented on JENKINS-21712 Jenkins Update breaks Subversion credential configuration Same problem here, reverting to version 1.54 of subversion plugin was my only option for now. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13357) Autoinstall JDK from download.oracle.com no longer works
Bruno Medeiros commented on JENKINS-13357 Autoinstall JDK from download.oracle.com no longer works Same problem here: Installing JDK jdk-7u40-oth-JPR Downloading JDK from http://download.oracle.com/otn/java/jdk/7u40-b43/jdk-7u40-linux-x64.tar.gz Downloading 5307bytes Installing /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh Sun_JDK_1.7 $ /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh -noregister /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 1: html: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 2: head: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 3: title: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 4: META: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 5: link: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 6: link: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 7: $'\r': command not found /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 8: body: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 9: div: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 10: table: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 11: tr: No such file or directory /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 12: syntax error near unexpected token `' /var/lib/jenkins/tools/hudson.model.JDK/Sun_JDK_1.7/jdk.sh: line 12: ` td rowspan="2" valign="middle" nowrapa href=""img src="" width="154" height="19" hspace="10" vspace="25" border="0" /a/td ' ERROR: Failed to install JDK. Exit code=2 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-20209) Maven plugin sends email notification to null address
Bruno Medeiros commented on JENKINS-20209 Maven plugin sends email notification to null address Where is it fixed? I'm on Jenkins 1.544, Maven Integration plugin 2.0 and still experiencing the issue. My downgrade option is to 1.533, not 1.534. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bruno Medeiros commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 Same problem here: java.lang.ClassFormatError: Failed to load hudson.maven.ProcessCache$GetSystemProperties It shouldn't be related to core using Java 6, it's a separated classloader, AFAIK. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Bruno Medeiros commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I have the same issue. Any expected release date for the pull request above? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13659) Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet)
[ https://issues.jenkins-ci.org/browse/JENKINS-13659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162932#comment-162932 ] Bruno Medeiros commented on JENKINS-13659: -- It seems to be fixed on Jenkins ver. 1.464, shouldn't you mark this ticket to this version? Migrating to Jenkins 1.462 : Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet) Key: JENKINS-13659 URL: https://issues.jenkins-ci.org/browse/JENKINS-13659 Project: Jenkins Issue Type: Bug Components: core, jclouds Affects Versions: current Environment: Tomcat 6.0.33 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03) Java HotSpot(TM) Server VM (build 1.5.0_22-b03, mixed mode) Solaris 2.10 Reporter: Laurent Schoelens Assignee: olamy Priority: Blocker Labels: exception, jenkins Can't start Jenkins 1.462 because of the following error on Java 5. SEVERE: Failed to initialize Jenkins java.lang.UnsupportedClassVersionError: Bad version number in .class file (unable to load class com.google.common.collect.ImmutableSet) at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:2822) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:1159) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1647) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1526) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) at hudson.security.PermissionScope.init(PermissionScope.java:70) at hudson.security.PermissionScope.clinit(PermissionScope.java:95) at hudson.security.Permission.init(Permission.java:179) at hudson.security.Permission.clinit(Permission.java:292) at jenkins.model.Jenkins.clinit(Jenkins.java:3817) at hudson.WebAppMain.installLogger(WebAppMain.java:256) at hudson.WebAppMain.contextInitialized(WebAppMain.java:107) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:592) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) May 2, 2012 12:30:44 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart May 2, 2012 12:30:44 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/hudson] startup failed due to previous errors Reverting to 1.461 solve the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8744) Maven cannot run with JDK1.5 anymore
[
https://issues.jenkins-ci.org/browse/JENKINS-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162933#comment-162933
]
Bruno Medeiros commented on JENKINS-8744:
-
@sogabe Thanks, it's ok for me now! It seems that my post is unrelated to this
bug, right?
Maven cannot run with JDK1.5 anymore
Key: JENKINS-8744
URL: https://issues.jenkins-ci.org/browse/JENKINS-8744
Project: Jenkins
Issue Type: Bug
Components: maven2
Reporter: Rainer Weinhold
Since an update to jenkins 1.395 the maven projects running with an JDK 1.5
arent working anymore.
The error Bad version number in .class file looks like something got
compiled with a newer java version. This error happens on a slave with maven
2.0.11 and oracle-jdk 1.5.21.
- When i reconfigure the project to oracle-jdk 1.6.20 it works.
- It also works with java 1.5 when executed directly on den shell.
- The only thing different there is the magic agent stuff.
So i extracted the jars : maven-interceptor, maven-agent, slave.jar,
classworlds. Non of which there seems to be a newer .class version number.
Any ideas which files could cause the problem? Pretty sure this is a jenkins
issue, otherwise maven wouldn't compile it directly on the build system.
LOG:
{noformat}
At revision 56650
no change for http://.../trunk since the previous build
Found mavenVersion 2.0.11 from file
jar:file:/srv/hudson/tools/maven-2.0.x/lib/maven-2.0.11-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
No emails were triggered.
Parsing POMs
[maven-versioninfo-plugin] $ /srv/hudson/tools/Java-1.5.x/bin/java -Xmx512m
-Xms64m -XX:PermSize=64m -XX:MaxPermSize=128m -cp
/srv/hudson/maven-agent.jar:/srv/hudson/classworlds.jar
hudson.maven.agent.Main /srv/hudson/tools/maven-2.0.x /srv/hudson/slave.jar
/srv/hudson/maven-interceptor.jar 44373
===[HUDSON REMOTING CAPACITY]===���channel started
channel stopped
ERROR: POMs konnten nicht geparst werden
java.io.IOException: Remote call on Channel to Maven
[/srv/hudson/tools/Java-1.5.x/bin/java, -Xmx512m, -Xms64m, -XX:PermSize=64m,
-XX:MaxPermSize=128m, -cp,
/srv/hudson/maven-agent.jar:/srv/hudson/classworlds.jar,
hudson.maven.agent.Main, /srv/hudson/tools/maven-2.0.x,
/srv/hudson/slave.jar, /srv/hudson/maven-interceptor.jar, 44373] failed
at hudson.remoting.Channel.call(Channel.java:638)
at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:665)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420)
at hudson.model.Run.run(Run.java:1362)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:424)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:145)
Caused by: java.lang.UnsupportedClassVersionError: Bad version number in
.class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.lang.ClassLoader.defineClass(ClassLoader.java:465)
at
hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:151)
at
hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at
hudson.plugins.cobertura.MavenCoberturaPublisher.clinit(MavenCoberturaPublisher.java:237)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at
sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:25)
at
sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:122)
at java.lang.reflect.Field.acquireFieldAccessor(Field.java:918)
at java.lang.reflect.Field.getFieldAccessor(Field.java:899)
at java.lang.reflect.Field.getLong(Field.java:528)
at
java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1586)
at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:52)
at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:408)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.init(ObjectStreamClass.java:400)
at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:531)
at
java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at
[JIRA] (JENKINS-8744) Maven cannot run with JDK1.5 anymore
[
https://issues.jenkins-ci.org/browse/JENKINS-8744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162891#comment-162891
]
Bruno Medeiros commented on JENKINS-8744:
-
Same error here, on Jenkins 1.463:
{code}
===[JENKINS REMOTING CAPACITY]===channel started
log4j:WARN No appenders could be found for logger
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
channel stopped
ERROR: Failed to parse POMs
java.io.IOException: Remote call on Channel to Maven
[/var/lib/jenkins/tools/Sun_JDK_1.5/bin/java, -cp,
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-agent-1.2.jar:/var/lib/jenkins/tools/Maven_2/boot/classworlds-1.1.jar,
hudson.maven.agent.Main, /var/lib/jenkins/tools/Maven_2,
/var/cache/jenkins/war/WEB-INF/lib/remoting-2.13.jar,
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven-interceptor-1.2.jar,
59378,
/var/lib/jenkins/plugins/maven-plugin/WEB-INF/lib/maven2.1-interceptor-1.2.jar]
failed
at hudson.remoting.Channel.call(Channel.java:655)
at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:156)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:791)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:480)
at hudson.model.Run.run(Run.java:1434)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.lang.ClassFormatError: Failed to load
com.google.common.collect.ImmutableSet
at
hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:154)
at
hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
at hudson.security.PermissionScope.init(PermissionScope.java:70)
at hudson.security.PermissionScope.clinit(PermissionScope.java:95)
at hudson.security.Permission.init(Permission.java:179)
at hudson.security.Permission.clinit(Permission.java:292)
at hudson.model.Run.clinit(Run.java:2038)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:74)
at hudson.maven.Maven2Builder.call(Maven2Builder.java:53)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:651)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:676)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class
file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.lang.ClassLoader.defineClass(ClassLoader.java:466)
at
hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:152)
... 20 more
Finished: FAILURE
/pre
{code}
Maven cannot run with JDK1.5 anymore
Key: JENKINS-8744
URL: https://issues.jenkins-ci.org/browse/JENKINS-8744
Project: Jenkins
Issue Type: Bug
Components: maven2
Reporter: Rainer Weinhold
Since an update to jenkins 1.395 the maven projects running with an JDK 1.5
arent working anymore.
The error Bad version number in .class file looks like something got
compiled with a newer java version. This error happens on a slave with maven
2.0.11 and oracle-jdk 1.5.21.
- When i reconfigure the project to oracle-jdk 1.6.20 it works.
- It also works with java 1.5 when executed directly on den shell.
- The only thing different there is the magic agent stuff.
So i extracted the jars : maven-interceptor, maven-agent, slave.jar,
classworlds. Non of which there seems to be a newer .class version number.
Any ideas which files could cause the problem? Pretty sure this is a jenkins
issue, otherwise maven wouldn't compile it directly on the build system.
LOG:
{noformat}
At revision 56650
no change for http://.../trunk since the previous build
Found mavenVersion 2.0.11 from file
