Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-15490

Analysis parsers don't work with maven 2 jobs

    Details

    • Similar Issues:

      Description

      In the latest version(1.485) of Jenkins with only Checkstyle plugin and Static Analysis Utilities/Static Analysis Collector Plug-in installed and no any other configuration change, enabling Publish Checkstyle analysis results in a maven 2 job type and use checkstyle:checkstyle as maven goal will get exception as below:

      [INFO] ------------------------------------------------------------------------
      [INFO] Trace
      org.apache.commons.logging.LogConfigurationException: java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl (Caused by java.lang.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl)
      	at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:637)
      	at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
      	at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704)
      	at org.apache.commons.digester.Digester.<init>(Digester.java:304)
      	at hudson.plugins.checkstyle.parser.CheckStyleParser.parse(CheckStyleParser.java:48)
      	at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:53)
      	at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:261)
      	at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:220)
      	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:169)
      	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)
      	at hudson.FilePath.act(FilePath.java:851)
      	at hudson.FilePath.act(FilePath.java:824)
      	at hudson.plugins.checkstyle.CheckStyleReporter.perform(CheckStyleReporter.java:120)
      	at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:313)
      	at hudson.maven.Maven2Builder.postExecute(Maven2Builder.java:155)
      	at hudson.maven.MavenBuilder$Adapter.postExecute(MavenBuilder.java:310)
      	at hudson.maven.agent.PluginManagerInterceptor$1MojoIntercepterImpl.callPost(PluginManagerInterceptor.java:170)
      	at hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:183)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
      	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
      	at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
      	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
      	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
      	at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
      	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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
      	at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
      	at hudson.maven.agent.Main.launch(Main.java:185)
      	at hudson.maven.MavenBuilder.call(MavenBuilder.java:151)
      	at hudson.maven.Maven2Builder.call(Maven2Builder.java:77)
      	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:326)
      	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
      	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.IllegalAccessError: tried to access class org.apache.commons.logging.impl.LogFactoryImpl$3 from class org.apache.commons.logging.impl.LogFactoryImpl
      	at org.apache.commons.logging.impl.LogFactoryImpl.getParentClassLoader(LogFactoryImpl.java:700)
      	at org.apache.commons.logging.impl.LogFactoryImpl.createLogFromClass(LogFactoryImpl.java:1187)
      	at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:914)
      	at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
      	... 46 more
      

        Attachments

          Issue Links

            Activity

            Hide
            drulli Ulli Hafner added a comment -

            I don't know if that is something that needs to be fixed in core or my plug-in. I would suspect that my plug-in needs to be fixed. Before I can make an estimation I need to look into that bug and try to reproduce it on my machine.

            Show
            drulli Ulli Hafner added a comment - I don't know if that is something that needs to be fixed in core or my plug-in. I would suspect that my plug-in needs to be fixed. Before I can make an estimation I need to look into that bug and try to reproduce it on my machine.
            Hide
            xstyle Justin Ye added a comment -

            Hi Ulli, how is this issue going on ? I am not sure how long this kind of issue usually takes, if it cannot be fixed in recent release. I may need to find another plan.
            Please let me know. Thanks.

            Show
            xstyle Justin Ye added a comment - Hi Ulli, how is this issue going on ? I am not sure how long this kind of issue usually takes, if it cannot be fixed in recent release. I may need to find another plan. Please let me know. Thanks.
            Hide
            drulli Ulli Hafner added a comment -

            I don't have spare time to work on a fix right now. So it would be good if you find a workaround for your setup...

            Show
            drulli Ulli Hafner added a comment - I don't have spare time to work on a fix right now. So it would be good if you find a workaround for your setup...
            Hide
            drulli Ulli Hafner added a comment -

            I tried some ideas to get the plug-in correctly running with maven 2, however nothing worked. I think that this actually is a problem in the classloader of the maven 2 plug-in in Jenkins core... Seems that they are new isolated enough.

            Show
            drulli Ulli Hafner added a comment - I tried some ideas to get the plug-in correctly running with maven 2, however nothing worked. I think that this actually is a problem in the classloader of the maven 2 plug-in in Jenkins core... Seems that they are new isolated enough.
            Hide
            drulli Ulli Hafner added a comment -

            I think maven 2 should not be supported anymore.

            Show
            drulli Ulli Hafner added a comment - I think maven 2 should not be supported anymore.

              People

              • Assignee:
                drulli Ulli Hafner
                Reporter:
                xstyle Justin Ye
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: