[JIRA] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
Title: Message Title Jesse Glick resolved as Duplicate Essentially a duplicate of JENKINS-25272. (BTW the Jenkins class loaders are in fact modular, as in OSGi. The problem here is that the slave agent shares code with the master, and the Maven plugin runs some of that same code also in the Maven process. It is just a foolish design.) Jenkins / JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
pmv commented on JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 I think these tickets are similar, in that users running builds expect to be able to compile with any JDK. However, the actual criteria seems to be this: If you are building using the Maven project type, the minimum JDK you can compile with is determined by the maximum of the following: The java version Jenkins core was compiled with The java version your container was compiled with (specifically, the servlet-api jar) The java version the maven-plugin was compiled with The versions for JENKINS-25272 are 1.6, 1.5, 1.5, so a 1.5 build broke due to be #1 (as I would consider the remoting jar to be part of core) The versions for JENKINS-16920 were 1.5, 1.6, 1.5, so a 1.5 build broke due to #2. The versions for this ticket are 1.6, 1.7, 1.5, so 1.6 builds break due to #2. We haven't actually seen #3, since it seems to be lagging behind the other two, but I suspect it is true. These restrictions make some sense once you understand that Jenkins plugin classloading is hierarchical (rather than using something like OSGi), so plugin developers probably understand this: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Structure#PluginStructure-Classloader However, the first time you encounter it as a user it's not intuitive (especially the servlet-api dependency). If a fix is not going to be made, at minimum I would suggest calling out these restrictions on the Maven project plugin wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin 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-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
Daniel Beck commented on JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 JENKINS-25272? 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-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
pmv created JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 14/Apr/15 10:50 PM Description: This seems to be a duplicate of JENKINS-16920, but a newer iteration. Due to the recent talk on the mailing list about removing 1.6 support, as well as the git plugin dropping 1.6 support, we decided to upgrade our Jenkins from running on Java 6/Tomcat 6 to Java 7/Tomcat 8. However, it appears Tomcat 8 ships a version of servlet-api built with Java 7. Jessie's original analysis on why this was a problem is here: https://issues.jenkins-ci.org/browse/JENKINS-16920?focusedCommentId=174350&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-174350 I suspect this is either the same or a very similar issue. Here is the stack trace: java.lang.reflect.InvocationTargetException 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178) 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:597) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ClassFormatError: Failed to load javax.servlet.ServletException at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:325) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at hudson.ExtensionList.lookup(ExtensionList.java:350) at hudson.FilePath.actAsync(FilePath.java:1046) at hudson.FilePath.copyRecursiveTo(FilePath.java:2070) at hudson.FilePath.copyRecursiveTo(FilePath.java:2013) at hudson.FilePath.copyRecursiveTo(FilePath.java:1996) at hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.si
