New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add @exception JavaDoc block tag to NonEmptyAtclauseDescriptionCheck #5388

Closed
sikhlev opened this Issue Dec 25, 2017 · 3 comments

Comments

Projects
None yet
3 participants
@sikhlev
Contributor

sikhlev commented Dec 25, 2017

@exception JavaDoc block tag is a part of the JavaDoc specification and it may not be empty.
Taken from #5092 .

@romani romani added the approved label Dec 25, 2017

@romani romani changed the title from Add @exception JavaDoc tag to NonEmptyAtclauseDescriptionCheck to Add @exception JavaDoc block tag to NonEmptyAtclauseDescriptionCheck Dec 25, 2017

@romani romani added the javadoc label Dec 25, 2017

sikhlev added a commit to epam/checkstyle that referenced this issue Dec 27, 2017

romani added a commit that referenced this issue Dec 27, 2017

@romani romani added the new feature label Dec 27, 2017

@romani romani added this to the 8.6 milestone Dec 27, 2017

@romani

This comment has been minimized.

Show comment
Hide comment
@romani

romani Dec 27, 2017

Member

fix is merged

Member

romani commented Dec 27, 2017

fix is merged

@romani

This comment has been minimized.

Show comment
Hide comment
@romani

romani Jan 6, 2018

Member

image

image

@ps-sp and @Vladlis
We need to update message to ask user to read specification of javadoc syntax .... nobody inthis world know it, it took me a while to understand what is missed and how to make Check work.

Member

romani commented Jan 6, 2018

image

image

@ps-sp and @Vladlis
We need to update message to ask user to read specification of javadoc syntax .... nobody inthis world know it, it took me a while to understand what is missed and how to make Check work.

@rnveach

This comment has been minimized.

Show comment
Hide comment
@rnveach

rnveach Jan 7, 2018

Member

@romani I moved this to a new issue so it doesn't get lost in this closed one.
See #5443

Member

rnveach commented Jan 7, 2018

@romani I moved this to a new issue so it doesn't get lost in this closed one.
See #5443

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment