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

ClassCastException when reports are created with maven-site-plugin

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: findbugs-plugin
    • Labels:
      None
    • Environment:
    • Similar Issues:

      Description

      When enabling the Jenkins Findbugs plugin on a Maven job that uses the maven-site-plugin to generate the reports then the build fails with the root cause exception:
      java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
      (cf. attachment for full stack-trace).

        Attachments

          Issue Links

            Activity

            Hide
            famod Falko Modler added a comment -

            Any updates? I just had to downgrade to maven-site-plugin 3.0.

            Show
            famod Falko Modler added a comment - Any updates? I just had to downgrade to maven-site-plugin 3.0.
            Hide
            drulli Ulli Hafner added a comment -

            @Falko: did you try the workaround noted by Thomas?

            This issue is not on my priority list So feel free to provide a patch if the workaround is not working in your environment...

            Show
            drulli Ulli Hafner added a comment - @Falko: did you try the workaround noted by Thomas? This issue is not on my priority list So feel free to provide a patch if the workaround is not working in your environment...
            Hide
            drulli Ulli Hafner added a comment -

            I tried some ideas to get the plug-in correctly running with new site plugin, however nothing worked. I think that this actually is a problem in the class loaders of the maven 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 new site plugin, however nothing worked. I think that this actually is a problem in the class loaders of the maven plug-in in Jenkins core... Seems that they are new isolated enough.
            Hide
            ahorst Andreas Horst added a comment -

            I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job.

            Show
            ahorst Andreas Horst added a comment - I can still confirm this on 1.574 with maven-site-plugin 3.3. Also the workaround to additionally invoke the default lifecycle (e.g. "clean package site-deploy") works. Though it would be nice to be able to just do a "clean site-deploy" in a dedicated site job.
            Hide
            kohsuke Kohsuke Kawaguchi added a comment -

            Dupliate of JENKINS-13709.

            Show
            kohsuke Kohsuke Kawaguchi added a comment - Dupliate of JENKINS-13709 .

              People

              • Assignee:
                kohsuke Kohsuke Kawaguchi
                Reporter:
                zlika Thomas Zlika
              • Votes:
                10 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: