|
||||||||
|
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... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) Publishing Findbugs... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) ClassCastException ... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) ClassCastException ... [email protected] (JIRA)
- [JIRA] (JENKINS-15344) ClassCastException ... [email protected] (JIRA)

"mvn clean site" works indeed with maven site plugin 3.0, but not with 3.1 or 3.2.
I have also found another workaround: the bug vanishes if instead of doing "mvn clean site" I do "mvn clean install site" !