[
https://issues.apache.org/jira/browse/HCATALOG-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411644#comment-13411644
]
Travis Crawford commented on HCATALOG-447:
------------------------------------------
Looking at the findbugs release dates, v2 was released 2011-12-21, while the
previous release 1.3.9 was released a couple years earlier (2009-08-21) and
surely has a much larger install base.
Which version do we want to support for HCatalog? Ideally the latest version,
but if people actually running this in CI or whatever have to use the previous
version we could do that instead.
Personally, unless detected errors break the build I'm not a big fan of stuff
like findbugs (and checkstyle) because there are no consequences for causing an
"error". If we're going to have a findbugs target, what do y'all think about
having our main CI target run this and fail if there are any discovered issues?
Of course, we'd need to make sure there's an error suppression feature.
> findbugs target doesn't work in trunk
> -------------------------------------
>
> Key: HCATALOG-447
> URL: https://issues.apache.org/jira/browse/HCATALOG-447
> Project: HCatalog
> Issue Type: Bug
> Components: build
> Affects Versions: 0.5
> Reporter: Alan Gates
> Assignee: Travis Crawford
> Fix For: 0.5
>
> Attachments: HCATALOG-447_fix_findbugs.1.patch
>
>
> Doing "ant findbugs" results in:
> {code}
> findbugs:
> [mkdir] Created dir: /Users/gates/src/hcat/top/trunk/build/test/findbugs
> BUILD FAILED
> /Users/gates/src/hcat/top/trunk/build.xml:477: findbugs doesn't support the
> nested "fileset" element.
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
