|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I'm having similar issues on a master jenkins.
My stacktrace looks more like the stack trace posted by Martin Burger - I pasted my Maven 3 stack trace in my comment on JENKINS-18441.
PS: switching on Findbugs with Maven 2 also fails the builds.
The Maven 2 build succeeds when disabling the Findbugs reporting option in the job's config.
But with Maven 2.2.1, I have an entirely different stacktrace, which may be unrelated to Findbugs (or not?)
In jenkins 1.518 the job succeeds with Findbugs reporting turned on. (but still the same stack trace there)