-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Windows 7
I just switched to Maven 3.1 and saw that Findbugs was not reported on the page of the job anymore. When I switch back to Maven 3.0 it works like always.
With Maven 3.1 I found two different warnings in the Logs:
WARN org.apache.maven.eventspy.internal.EventSpyDispatcher - Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Failed to load edu.umd.cs.findbugs.detect.TestASM
WARN org.apache.maven.eventspy.internal.EventSpyDispatcher - Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Could not initialize class edu.umd.cs.findbugs.SortedBugCollection
Jenkins version: 1.526
Jenkins Findbugs Plugin version: 4.49
Findbugs Maven Plugin version: 2.5.2
- depends on
-
JENKINS-15935 Can't build using maven 3.1.0
-
- Resolved
-
- is duplicated by
-
JENKINS-26968 No Reports with Maven 3.1.1 or Maven 3.2.5
-
- Resolved
-
- is related to
-
JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
-
- Closed
-
I'm wondering if it still makes sense to continue development of the maven job type in my plugins. There are so many class loading issues that should be resolved automatically if the freestyle builder would be used instead... Maybe I should use the same approach as in the warnings plug-in, one publisher for both the maven and the freestyle job.