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

ClassNotFoundException: hudson.maven.MavenReporter -> failed to scout MavenCoberturaPublisher

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • cobertura-plugin
    • None

      After updating to the latest Jenkins (2.62) the following error appears in the log.

      Failed to scout hudson.plugins.cobertura.MavenCoberturaPublisher
java.lang.ClassNotFoundException: hudson.maven.MavenReporter
	at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374)
	at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
	at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
Caused: java.lang.NoClassDefFoundError: hudson/maven/MavenReporter
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
	at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1140)
	at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:884)
	at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1311)
	at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1364)
	at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44)
	at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:81)
	at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:1861)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at net.java.sezpoz.IndexItem.element(IndexItem.java:134)
Caused: java.lang.InstantiationException
	at net.java.sezpoz.IndexItem.element(IndexItem.java:146)
	at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:656)
	at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:471)
	at hudson.ExtensionList.load(ExtensionList.java:365)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:303)
	at hudson.ExtensionList.getComponents(ExtensionList.java:168)
	at jenkins.model.Jenkins$8.onInitMilestoneAttained(Jenkins.java:1119)
	at jenkins.InitReactorRunner$1.onAttained(InitReactorRunner.java:82)
	at org.jvnet.hudson.reactor.ReactorListener$Aggregator.onAttained(ReactorListener.java:104)
	at org.jvnet.hudson.reactor.Reactor$1.run(Reactor.java:176)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)}}

       

          [JENKINS-44415] ClassNotFoundException: hudson.maven.MavenReporter -> failed to scout MavenCoberturaPublisher

          Cyrille Le Clerc added a comment - - edited

          markl_lagendijk there seem to be a hudson.plugins.cobertura.MavenCoberturaPublisher that is related to hudson.maven.MavenReporter.

          Note that the pipeline-maven-plugin does NOT use hudson.maven.MavenReporter and is not related to the Cobertura plugin to my knowledge.

          However, we have recently introduced an optional dependency to the org.jenkins-ci.main:maven-plugin:2.14 for future integration with the settings of the maven-plugin pom.xml#L81: JENKINS-43650

          Note that teilo changed his mind and eventually did recommend to NOT introduce this dependency. If your issue confirms that there are side effects, I'll remove the dependency.

          markl_lagendijk can you please

          • check the startup logs for error message related to the loading of the maven-plugin or of any other plugin?
          • share with us the list of plugins that are loaded in your master and the exact version of core?
          • explain us how the cobertura plugin is used on your instance? in your pipelines?

          Seem to be a duplicate of JENKINS-44200 or caused by JENKINS-43650

          Cyrille Le Clerc added a comment - - edited markl_lagendijk there seem to be a hudson.plugins.cobertura.MavenCoberturaPublisher that is related to hudson.maven.MavenReporter . Note that the pipeline-maven-plugin does NOT use hudson.maven.MavenReporter and is not related to the Cobertura plugin to my knowledge. However , we have recently introduced an optional dependency to the org.jenkins-ci.main:maven-plugin:2.14 for future integration with the settings of the maven-plugin pom.xml#L81 : JENKINS-43650 Note that teilo changed his mind and eventually did recommend to NOT introduce this dependency. If your issue confirms that there are side effects, I'll remove the dependency. markl_lagendijk can you please check the startup logs for error message related to the loading of the maven-plugin or of any other plugin? share with us the list of plugins that are loaded in your master and the exact version of core? explain us how the cobertura plugin is used on your instance? in your pipelines? Seem to be a duplicate of JENKINS-44200 or caused by JENKINS-43650

          Mark Lagendijk added a comment -

          This is what happened:

          1. I updated to the latest Jenkins core version (2.62)
          2. After the restart I updated a few plugins, among which the pipeline-maven-plugin.
          3. After the restart pipeline builds did not resume. In the log we found the mentioned error.
          4. Restarting Jenkins normally (via the webinterface) did not work anymore. Jenkins would not come up.
          5. When I downgraded pipeline-maven-plugin everything was working again.

          Based on this I assumed the following:

          1. The problems with Jenkins are related to the mentioned error.
          2. The problems are related to the pipeline-maven-plugin

          However, today the problems re-appeared (while still having the downgraded pipeline-maven-plugin). So it turns out that at least the 2nd assumption is incorrect.

          Possibly the first one is also incorrect.

          I will now uninstall the Cobertura plugin and see if that fixes the issues.

          Mark Lagendijk added a comment - This is what happened: I updated to the latest Jenkins core version (2.62) After the restart I updated a few plugins, among which the pipeline-maven-plugin. After the restart pipeline builds did not resume. In the log we found the mentioned error. Restarting Jenkins normally (via the webinterface) did not work anymore. Jenkins would not come up. When I downgraded pipeline-maven-plugin everything was working again. Based on this I assumed the following: The problems with Jenkins are related to the mentioned error. The problems are related to the pipeline-maven-plugin However, today the problems re-appeared (while still having the downgraded pipeline-maven-plugin). So it turns out that at least the 2nd assumption is incorrect. Possibly the first one is also incorrect. I will now uninstall the Cobertura plugin and see if that fixes the issues.

          Mark Lagendijk added a comment -

          I closed this issue as a duplicate. Looks like the actual problems may be caused by the prioritysorter-plugin.

          Mark Lagendijk added a comment - I closed this issue as a duplicate. Looks like the actual problems may be caused by the prioritysorter-plugin .

            cleclerc Cyrille Le Clerc
            markl_lagendijk Mark Lagendijk
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: