[
https://issues.apache.org/jira/browse/ZOOKEEPER-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096291#comment-13096291
]
Thomas Koch commented on ZOOKEEPER-1170:
----------------------------------------
The eclipse compiler can also be included in builds to just produce its
warnings. But it would make sense to make the maven migration first before
thinking about including it.
See http://thecoderlounge.blogspot.com/2010/05/ecj-eclipse-java-compiler.html
The maven info is
<groupId>org.eclipse.jdt.core.compiler</groupId>
<artifactId>ecj</artifactId>
<version>3.7</version>
And there's a plugin to show the warnings in jenkins:
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
> Fix compiler (eclipse) warnings: unused imports, unused variables, missing
> generics
> -----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1170
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1170
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Thomas Koch
> Assignee: Thomas Koch
> Priority: Minor
> Attachments: ZOOKEEPER-1170.patch
>
>
> IDE warnings get useless if there are too many of them. This issue + patch
> fixes nearly the rest of them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
