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

        1. findbugs-maven-example.zip
          45 kB
        2. jenkins.log
          116 kB
        3. pluginversions.jpg
          pluginversions.jpg
          224 kB

          [JENKINS-19096] Findbugs Reporting not working with Maven 3.1

          Ulli Hafner added a comment -

          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.

          Ulli Hafner added a comment - 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.

          Mark Waite added a comment -

          I fear that the outcry will be very loud if you stop supporting the maven job type in your plugins. I wish it were different, but I'm sure there are many Jenkins users who use the maven job type and are critically dependent on your plugins. If you stop supporting the maven job type, they'll be very frustrated.

          Mark Waite added a comment - I fear that the outcry will be very loud if you stop supporting the maven job type in your plugins. I wish it were different, but I'm sure there are many Jenkins users who use the maven job type and are critically dependent on your plugins. If you stop supporting the maven job type, they'll be very frustrated.

          Ulli Hafner added a comment -

          Sorry, this was not precise and needs some clarification: if I remove the special maven handling then the plug-in will still be usable in maven and freestyle jobs. Currently the findbugs plugin uses two different implementations: one gets instantiated by freestyle jobs and the other by maven jobs. In the warnings plugin I'm having only one implementation that is instantiated for both build types. This makes coding and testing much easier (DRY) and has no classloading problems. The only benefit for having a special maven implementation is to derive the filename of the findbugs warnings from the pom.

          Ulli Hafner added a comment - Sorry, this was not precise and needs some clarification: if I remove the special maven handling then the plug-in will still be usable in maven and freestyle jobs. Currently the findbugs plugin uses two different implementations: one gets instantiated by freestyle jobs and the other by maven jobs. In the warnings plugin I'm having only one implementation that is instantiated for both build types. This makes coding and testing much easier (DRY) and has no classloading problems. The only benefit for having a special maven implementation is to derive the filename of the findbugs warnings from the pom.

          Mark Waite added a comment -

          I see. Removing the special case handling for maven type jobs seems very reasonable to me. I don't know how you would perform the migration in the plugin, but I assume even that is possible, since the pom must contain the information you need.

          Mark Waite added a comment - I see. Removing the special case handling for maven type jobs seems very reasonable to me. I don't know how you would perform the migration in the plugin, but I assume even that is possible, since the pom must contain the information you need.

          Vadim Dedkov added a comment - - edited

          My parameters:
          Jenkins version: 1.544
          Jenkins Findbugs Plugin version: 4.56
          Findbugs Maven Plugin version: 2.5.2

          When I put in goals and options in settings of my job "clean org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U"
          I didn'n find findbugs icon and findbugs*.xml-files in build directory,
          but when I put "clean install org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U"
          I found findbugs icon and findbugs*.xml-files in build directory of my project.

          That is, when I put "install" then findbugs started working.

          Vadim Dedkov added a comment - - edited My parameters: Jenkins version: 1.544 Jenkins Findbugs Plugin version: 4.56 Findbugs Maven Plugin version: 2.5.2 When I put in goals and options in settings of my job "clean org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I didn'n find findbugs icon and findbugs*.xml-files in build directory, but when I put "clean install org.codehaus.mojo:findbugs-maven-plugin:2.5.2:findbugs deploy -U" I found findbugs icon and findbugs*.xml-files in build directory of my project. That is, when I put "install" then findbugs started working.

          Daan Hoogland added a comment -

          H all, I started noticing this on jenkins.buildacloud.org (the apache cloudstack ci). I reproduced the job we have there internally at Schuberg Philis. There it does produce reports on the enterprise jenkins. I am triaging the differences but not hopefull as most of the obvious have passed. Any progress on this issue yet? Let me know if I can help with further info.

          Daan, also reachable as dhoogland at our company name without the space dot com

          Daan Hoogland added a comment - H all, I started noticing this on jenkins.buildacloud.org (the apache cloudstack ci). I reproduced the job we have there internally at Schuberg Philis. There it does produce reports on the enterprise jenkins. I am triaging the differences but not hopefull as most of the obvious have passed. Any progress on this issue yet? Let me know if I can help with further info. Daan, also reachable as dhoogland at our company name without the space dot com

          Ulli Hafner added a comment -

          @Daan: Currently there are no plans to fix the class loading issues of the maven plug-in. Please use a freestyle project until I find some time to migrate my plug-in actions so they do not require the maven plug-in anymore.

          Ulli Hafner added a comment - @Daan: Currently there are no plans to fix the class loading issues of the maven plug-in. Please use a freestyle project until I find some time to migrate my plug-in actions so they do not require the maven plug-in anymore.

          podskalsky added a comment -

          I can't accept "switch to the freestyle project" !

          A freestyle project has not the requered extended Maven features which are used by our projects.

          For example:

          POM_* variables from pom.xml are missing in env
          MAVEN_HOME variable is missing in env
          Artifactory-Plugin is not able to find artifacts in freestyle project
          artifacts have different names like at maven project (at finalName was ignored at freestyle project - name was artifacId)
          collecting reports (checkstyle, pmd, findbugs, junit, jacoco, ...) is not easy
          ...

          podskalsky added a comment - I can't accept "switch to the freestyle project" ! A freestyle project has not the requered extended Maven features which are used by our projects. For example: POM_* variables from pom.xml are missing in env MAVEN_HOME variable is missing in env Artifactory-Plugin is not able to find artifacts in freestyle project artifacts have different names like at maven project (at finalName was ignored at freestyle project - name was artifacId) collecting reports (checkstyle, pmd, findbugs, junit, jacoco, ...) is not easy ...

          Mark Waite added a comment -

          podskalsky, since this is an open source project, you're welcome to submit pull requests. There is a wiki page that will help you get started as a Jenkins developer. Don't forget to include tests of your changes (as recommended in that wiki page).

          Mark Waite added a comment - podskalsky , since this is an open source project, you're welcome to submit pull requests. There is a wiki page that will help you get started as a Jenkins developer. Don't forget to include tests of your changes (as recommended in that wiki page).

          Ulli Hafner added a comment -

          This issue is also fixed by pull request for JENKINS-26923.

          Ulli Hafner added a comment - This issue is also fixed by pull request for JENKINS-26923 .

            drulli Ulli Hafner
            achbine Sabine Achilles
            Votes:
            17 Vote for this issue
            Watchers:
            30 Start watching this issue

              Created:
              Updated:
              Resolved: