You don't need a lot of tooling for a quick sanity check if you expose only what you want to expose from a #Java package. Generate your #Javadoc and see what it sees and publishes. Its default inclusions are just spot on.

Also, if you ever wondered why #SpringJavaFormat / #Checkstyle ask the first sentence of a type-level JavaDoc comment to end with a period, the screenshot shows why :)

It will become the value of `Description` in the overview.

@rotnroll666 which is not specific to either springsomething or checkstyle, but just the case since javadoc was released with jdk in the 1990s.

There is even more, like that third person mood that makes the <subject> Does this and that. Which was supposed to be read easier. I still consider Sun's style guide pretty useful and timeless.

@rotnroll666 and here I thought I am the only one. I use this method too. Better than what IDEs offer. Best visual indicator of what is visible to others.
@raupach exactly that. Quick visual easy to grasp.