[ 
https://issues.apache.org/jira/browse/CASSANDRA-18239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718214#comment-17718214
 ] 

Ekaterina Dimitrova commented on CASSANDRA-18239:
-------------------------------------------------

According to the ErrorProne instruction 
[here|https://errorprone.info/docs/installation], we would need these artifacts:
- error_prone_core-${EP_VERSION?}-with-dependencies.jar 
fromhttps://repo1.maven.org/maven2/com/google/errorprone/error_prone_core/
- dataflow-errorprone-${DATAFLOW_VERSION}.jar 
fromhttps://repo1.maven.org/maven2/org/checkerframework/dataflow-errorprone/

Unfortunately dataflow-errorprovne is GPL2 license so I think in this case we 
are not allowed to use ErrorProne if I am reading correctly 
[here|https://www.apache.org/licenses/GPL-compatibility.html]


> Replace eclipse warnings based static code analysis with something better 
> (Sonar)
> ---------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18239
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18239
>             Project: Cassandra
>          Issue Type: Task
>          Components: Build
>            Reporter: Jacek Lewandowski
>            Priority: Normal
>
> Eclipse warnings is used for static code analysis. However, it does not fit 
> well into Cassandra code and practically we end up explicitly adding 
> suppressions in many places just to satisfy that tool rather than fix the 
> real issues.
> This is an incomplete list of reasons to remove it:
> - not closed resources are detected incorrectly
> - does not recognize custom utility methods used to close the resources, 
> which use use heavily in the code, like {{Throwables.close}}, 
> {{FileUtils.close}}, {{closeQuietly}}...
> - because of the above, we cannot make important things like {{Ref}} to 
> implement {{Closeable}} as it would make the tool to explode with tons of 
> warnings
> - it complains about correct generics - something like "method X is not 
> applicable for ..." when the code compiles successfully is not acceptable
> - it is old and not maintained
> There are better tools like IntelliJ inspections for example, which can also 
> be run in headless mode



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to