|
||||||||
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 |
[JIRA] (JENKINS-15344) Publishing Findbugs analysis report on a multi-module maven project results in ClassCastException
zlika_...@hotmail.com (JIRA) Sun, 30 Sep 2012 03:54:54 -0700
- [JIRA] (JENKINS-15344) Publishing Findbugs... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... scm_issue_l...@java.net (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... ullrich.haf...@gmail.com (JIRA)
- [JIRA] (JENKINS-15344) Publishing Fin... zlika_...@hotmail.com (JIRA)
- [JIRA] (JENKINS-15344) ClassCastExcep... ullrich.haf...@gmail.com (JIRA)
According to the stack trace, it seems to be a class loading problem with dom4j.
Using mvn dependency:tree, we can see that dom4j is used twice with 2 slightly different versions:
In FindBugsParser.readXml(), where the bug occurs, you change the context class loader. And I can see in the stack trace that an async task is launched in a ThreadPoolExecutor, so the thread in the executor is certainly not using the class loader you tried to impose in FindBugsParser.readXml(), isn't it ?
Maybe a quick-and-dirty workaround would be to explicitly exclude dom4j:dom4j:jar:1.6.1 when configuring the findbugs dependency ?