[
https://issues.apache.org/jira/browse/YETUS-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462846#comment-17462846
]
Mike Drob commented on YETUS-557:
---------------------------------
There's a few annoyances that I have with check style here - 1) the
DesignForExtension rule doesn't respect Override annotations so I manually have
to create an empty javadoc with inheritDoc tag which is annoying and 2)
JavadocVariable requires me to comment all of the private variables I use. I
supposed both of these are fine, but they add some boilerplate to the code
which would be easily avoidable, can we tune down the aggressiveness of check
style?
Also, I'd like to add some java unit tests for this since I was taking a second
look at my exclusion logic and I'm not sure it's completely correct. Is there a
preferred framework/version to use, or do I get my choice since I'm the first
one in the area?
> Investigate switching to jdk.javadoc.doclet
> -------------------------------------------
>
> Key: YETUS-557
> URL: https://issues.apache.org/jira/browse/YETUS-557
> Project: Yetus
> Issue Type: Task
> Components: Audience Annotations
> Affects Versions: 0.6.0
> Reporter: Allen Wittenauer
> Assignee: Mike Drob
> Priority: Major
> Attachments: 0001-Remove-JDK8.patch, YETUS-557.00.patch,
> YETUS-557.01.patch
>
>
> It looks like there is a newer API available for building Javadoc doclets.
> This might help remove our dependency on tools.jar.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
