[
https://issues.apache.org/jira/browse/CASSANDRA-13175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156593#comment-16156593
]
Marcus Eriksson commented on CASSANDRA-13175:
---------------------------------------------
the error is because {{ant errorprone}} does not generate a junit xml which we
try to collect later, fix
[here|https://github.com/krummas/cassandra/commit/2beae60a1189b90515f093ef46fa4214e529f187]
- circle running [here|https://circleci.com/gh/krummas/cassandra/107]
> Integrate "Error Prone" Code Analyzer
> -------------------------------------
>
> Key: CASSANDRA-13175
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13175
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Attachments: 0001-Add-Error-Prone-code-analyzer.patch,
> checks-2_2.out, checks-3_0.out, checks-trunk.out
>
>
> I've been playing with [Error Prone|http://errorprone.info/] by integrating
> it into the build process and to see what kind of warnings it would produce.
> So far I'm positively impressed by the coverage and usefulness of some of the
> implemented checks. See attachments for results.
> Unfortunately there are still some issues on how the analyzer is effecting
> generated code and used guava versions, see
> [#492|https://github.com/google/error-prone/issues/492]. In case those issues
> have been solved and the resulting code isn't affected by the analyzer, I'd
> suggest to add it to trunk with warn only behaviour and some less useful
> checks disabled. Alternatively a new ant target could be added, maybe with
> build breaking checks and CI integration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
