Skip to content

Conversation

dimas-b
Copy link
Contributor

@dimas-b dimas-b commented Oct 1, 2025

This is to fix javadoc error: No public or protected classes found to document

snazy
snazy previously approved these changes Oct 2, 2025
Copy link
Member

@snazy snazy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't mind this change per-se.
Generally I think it is better to keep implementations as "protected" as possible.

JavaPoolAsyncExec is public only for testing purposes.

Can we update the javadoc to just not emit the warning? Or let javadoc emit docs for package-protected types ((options as StandardJavadocDocletOptions).showFromPackage())

@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Oct 2, 2025
@dimas-b
Copy link
Contributor Author

dimas-b commented Oct 3, 2025

Can we update the javadoc to just not emit the warning [...]

Sadly, it's an "error" (shows up pretty prominently in IJ)... I'll see about addressing it without making the class public.

image

@dimas-b dimas-b marked this pull request as draft October 3, 2025 17:12
This is to fix javadoc error: `No public or protected classes found to document`
@dimas-b dimas-b changed the title Make VertxAsyncExec public Increase javadoc visibility in :polaris-async-vertx Oct 3, 2025
@dimas-b dimas-b requested review from adnanhemani and snazy October 3, 2025 17:22
@dimas-b dimas-b marked this pull request as ready for review October 3, 2025 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants