[
https://issues.apache.org/jira/browse/DRILL-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16585832#comment-16585832
]
Vitalii Diravka edited comment on DRILL-6677 at 8/20/18 3:09 PM:
-----------------------------------------------------------------
Looks like currently this is the issue with Drill Maven check-style and it is
not related to specific IDE.
Can be reproduced with adding `LogicalFilter` to import statements in
DrillRelFactories and {{mvn clean install -DskipTests}}
was (Author: vitalii):
Looks like currently this is the issue with Drill Maven check-style and it is
related to specific IDE.
Can be reproduced with adding `LogicalFilter` to import statements in
DrillRelFactories and {{mvn clean install -DskipTests}}
> Check style reports JavaDocs imports only statements as unused
> --------------------------------------------------------------
>
> Key: DRILL-6677
> URL: https://issues.apache.org/jira/browse/DRILL-6677
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.15.0
> Reporter: Paul Rogers
> Priority: Major
>
> Consider the following Java snippet:
> {code}
> import com.foo.Bar;
> /**
> This is a reference to {@link com.foo.Bar}
> {code}
> Eclipse will notice the reference to {{com.foo.Bar}} in the Javadoc comment
> and its automatic import fixer-upper will include the import.
> But, check style appears to ignore Javadoc imports. So, Check style reports
> the import as unused.
> The only way, at present, to make Check style happy is to turn off the
> Eclipse import fixer-upper and do everything manually.
> Request: modify check style to also check for class references in Javadoc
> comments as such references are required for the Javadoc to build.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
