[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-1793:
--
Priority: Blocker (was: Major)
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Sub-task
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhishek Bafna updated OOZIE-1793:
--
Attachment: OOZIE-1793-01.patch
Attaching the rebase patch.
verified the patch with {{mvn clean verify -DskipTests}}.
+1 {{non-binding}}.
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Sub-task
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793-01.patch, OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
abhishek bafna updated OOZIE-1793:
--
Fix Version/s: 4.3.0
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Sub-task
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Fix For: 4.3.0
>
> Attachments: OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1793:
-
Issue Type: Sub-task (was: Improvement)
Parent: OOZIE-2036
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Sub-task
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1793:
-
Attachment: OOZIE-1793.patch
The new patch fixes the typo. I also fixed the plugin dependency, which had
the wrong groupId and version; though Maven was using the right plugin and
version before anyway.
NetBeans doesn't complain about those configs. And {{mvn verify -DskipTests}}
works fine. From what little I could find on the internet, some configs were
removed in some version of the plugin and added back later. It's possible that
due to the version misconfig I mentioned above, that IntelliJ was looking at an
older version of the plugin and complaining, while NetBeans and Maven were
picking up the latest version of the plugin and were okay with them. Can you
check again now that I fixed it?
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Improvement
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-1793.patch, OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1793:
-
Description:
I couldn't figure out how to run findbugs against Oozie. And even if it does
work, it looks like it's just going to create an XML file.
Based on some minor refactoring to this
[tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
and this [stack overflow
message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
I was able to improve our findbugs reporting. Now, when you run {{mvn
verify}} (which we use to generate a checkstyle report), it will also run
findbugs and transform the resulting XML files into html files that are human
readable.
The hard part here will be actually going through the reports and fixing these
bugs; but that's for other JIRAs :)
was:
I couldn't figure out how to run findbugs against Oozie. And even if it does
work, it looks like it's just going to create an XML file.
Based on some minor refactoring to this
[tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
and this [stack overflow
message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
I was able to improve our findbugs reporting. Now, when you run {{mvn
verify}} (which we use to generate a checkstyle report), it will also run
findbugs and transform the resulting XML files into html files that are human
readable.
The hard part here will be actually going through the reports and fixing these
bugs :)
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Improvement
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs; but that's for other JIRAs :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (OOZIE-1793) Improve find bugs reporting for Oozie
[
https://issues.apache.org/jira/browse/OOZIE-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-1793:
-
Attachment: OOZIE-1793.patch
> Improve find bugs reporting for Oozie
> -
>
> Key: OOZIE-1793
> URL: https://issues.apache.org/jira/browse/OOZIE-1793
> Project: Oozie
> Issue Type: Improvement
> Components: build
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: OOZIE-1793.patch
>
>
> I couldn't figure out how to run findbugs against Oozie. And even if it does
> work, it looks like it's just going to create an XML file.
> Based on some minor refactoring to this
> [tutorial|http://www.petrikainulainen.net/programming/maven/findbugs-maven-plugin-tutorial/]
> and this [stack overflow
> message|http://stackoverflow.com/questions/7035112/any-easy-way-to-generate-a-findbug-html-report-from-maven-without-sitesite/10365954#10365954],
> I was able to improve our findbugs reporting. Now, when you run {{mvn
> verify}} (which we use to generate a checkstyle report), it will also run
> findbugs and transform the resulting XML files into html files that are human
> readable.
> The hard part here will be actually going through the reports and fixing
> these bugs :)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
