-
Bug
-
Resolution: Duplicate
-
Minor
-
None
-
The problem occurs at least on the following tested environments:
- Jenkins 1.483 & 1.437 on both Windows and Linux
- analysis-core plugin 1.47 and findbugs plugin 4.44
- Multi-module Maven 3 project using Maven Findbugs plugin 2.5.2
- JDK 1.7 or JRE1.6
- Jenkins launched in standalone mode (java -jar jenkins.war) or deployed in a Tomcat server
- It is not a slave buildThe problem occurs at least on the following tested environments: - Jenkins 1.483 & 1.437 on both Windows and Linux - analysis-core plugin 1.47 and findbugs plugin 4.44 - Multi-module Maven 3 project using Maven Findbugs plugin 2.5.2 - JDK 1.7 or JRE1.6 - Jenkins launched in standalone mode (java -jar jenkins.war) or deployed in a Tomcat server - It is not a slave build
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).
- is duplicated by
-
JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation
- Resolved
- is related to
-
JENKINS-7666 ClassCastException parsing JUnit result
- Resolved
-
JENKINS-13709 ClassCast Exception when parsing JUnit surefire reports during website generation
- Resolved
-
JENKINS-14737 maven-site-plugin 3.1 causes Static Analysis Utilities not to display any results
- Resolved
-
JENKINS-17488 java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult
- Open