|
cristalp created JENKINS-12853:
---------------------------------- Summary: The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin Key: JENKINS-12853 URL: https://issues.jenkins-ci.org/browse/JENKINS-12853 Project: Jenkins Issue Type: Bug Components: findbugs Affects Versions: current Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, Jenkins Findbugs Plugin 4.33 Reporter: cristalp Assignee: Ulli Hafner When using the Maven2/3 job type, the Findbugs XML file isn't found. However, it is found under the following circumstances: * Using a free-style build * Adding {{<findbugsXmlOutput>true</findbugsXmlOutput>}} to the Maven Findbugs configuration. But this parameter [has been deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html]. From the Maven site, it's not very clear what its behavior is: {{This has been deprecated and is on by default. Default value is: false.}} Even though the generated files are the same, the plugin seems to search for the XML files in a different way. Here's the output when the XML files are not found: {code} [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- [INFO] Fork Value is true [java] Warnings generated: 4 [INFO] Done FindBugs Analysis.... [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module Implementation of Base Services with 0 warnings. {code} Here's the output when the XML files are found: {code} [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- [java] Warnings generated: 4 [INFO] Done FindBugs Analysis.... [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of module Implementation of Base Services with 4 warnings. {code} Also see the [discussion on the mailing list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
[ https://issues.jenkins-ci.org/browse/JENKINS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159862#comment-159862 ] SCM/JIRA link daemon commented on JENKINS-12853: ------------------------------------------------ Code changed in jenkins User: Ulli Hafner Path: plugin/src/main/java/hudson/plugins/findbugs/FindBugsPlugin.java plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java plugin/src/test/java/hudson/plugins/findbugs/FindBugsPluginTest.java http://jenkins-ci.org/commit/findbugs-plugin/2d80d625949524a81794ae0b4249872f94feb556 Log: [FIXED JENKINS-12853] Always use findbugsXml.xml when findbugs-maven-plugin version >= 2.4.0 is used. > The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin > --------------------------------------------------------------------------------- > > Key: JENKINS-12853 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12853 > Project: Jenkins > Issue Type: Bug > Components: findbugs > Affects Versions: current > Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, Jenkins Findbugs Plugin 4.33 > Reporter: cristalp > Assignee: Ulli Hafner > > When using the Maven2/3 job type, the Findbugs XML file isn't found. However, it is found under the following circumstances: > * Using a free-style build > * Adding {{<findbugsXmlOutput>true</findbugsXmlOutput>}} to the Maven Findbugs configuration. But this parameter [has been deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html]. From the Maven site, it's not very clear what its behavior is: {{This has been deprecated and is on by default. Default value is: false.}} > Even though the generated files are the same, the plugin seems to search for the XML files in a different way. > Here's the output when the XML files are not found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [INFO] Fork Value is true > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module Implementation of Base Services with 0 warnings. > {code} > Here's the output when the XML files are found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of module Implementation of Base Services with 4 warnings. > {code} > Also see the [discussion on the mailing list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12853. -------------------------------------------- Resolution: Fixed > The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin > --------------------------------------------------------------------------------- > > Key: JENKINS-12853 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12853 > Project: Jenkins > Issue Type: Bug > Components: findbugs > Affects Versions: current > Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, Jenkins Findbugs Plugin 4.33 > Reporter: cristalp > Assignee: Ulli Hafner > > When using the Maven2/3 job type, the Findbugs XML file isn't found. However, it is found under the following circumstances: > * Using a free-style build > * Adding {{<findbugsXmlOutput>true</findbugsXmlOutput>}} to the Maven Findbugs configuration. But this parameter [has been deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html]. From the Maven site, it's not very clear what its behavior is: {{This has been deprecated and is on by default. Default value is: false.}} > Even though the generated files are the same, the plugin seems to search for the XML files in a different way. > Here's the output when the XML files are not found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [INFO] Fork Value is true > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module Implementation of Base Services with 0 warnings. > {code} > Here's the output when the XML files are found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of module Implementation of Base Services with 4 warnings. > {code} > Also see the [discussion on the mailing list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
In reply to this post by JIRA noreply@jenkins-ci.org
[ https://issues.jenkins-ci.org/browse/JENKINS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159863#comment-159863 ] dogfood commented on JENKINS-12853: ----------------------------------- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_findbugs #388|http://ci.jenkins-ci.org/job/plugins_findbugs/388/] [FIXED JENKINS-12853] Always use findbugsXml.xml when (Revision 2d80d625949524a81794ae0b4249872f94feb556) Result = SUCCESS Ulli Hafner : Files : * plugin/src/test/java/hudson/plugins/findbugs/FindBugsPluginTest.java * plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java * plugin/src/main/java/hudson/plugins/findbugs/FindBugsPlugin.java > The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin > --------------------------------------------------------------------------------- > > Key: JENKINS-12853 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12853 > Project: Jenkins > Issue Type: Bug > Components: findbugs > Affects Versions: current > Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, Jenkins Findbugs Plugin 4.33 > Reporter: cristalp > Assignee: Ulli Hafner > > When using the Maven2/3 job type, the Findbugs XML file isn't found. However, it is found under the following circumstances: > * Using a free-style build > * Adding {{<findbugsXmlOutput>true</findbugsXmlOutput>}} to the Maven Findbugs configuration. But this parameter [has been deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html]. From the Maven site, it's not very clear what its behavior is: {{This has been deprecated and is on by default. Default value is: false.}} > Even though the generated files are the same, the plugin seems to search for the XML files in a different way. > Here's the output when the XML files are not found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [INFO] Fork Value is true > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module Implementation of Base Services with 0 warnings. > {code} > Here's the output when the XML files are found: > {code} > [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl --- > [java] Warnings generated: 4 > [INFO] Done FindBugs Analysis.... > [FINDBUGS] Parsing 1 files in /ige/jenkins/work/jobs/base/workspace/base-impl/target > [FINDBUGS] Successfully parsed file /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of module Implementation of Base Services with 4 warnings. > {code} > Also see the [discussion on the mailing list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira |
| Powered by Nabble | See how NAML generates this page |
