Skip to content

fix: resolve Javadoc warnings#8

Merged
marevol merged 1 commit into
mainfrom
fix/javadoc-warnings
Jun 13, 2026
Merged

fix: resolve Javadoc warnings#8
marevol merged 1 commit into
mainfrom
fix/javadoc-warnings

Conversation

@marevol

@marevol marevol commented Jun 13, 2026

Copy link
Copy Markdown
Contributor

Resolves all Javadoc warnings reported by mvn clean javadoc:javadoc (269 in total: 178 "no comment", 80 "no main description", plus a handful of missing/empty @param/@return tags and default-constructor warnings) across 34 files in the core and toolkit modules.

Changes are Javadoc-only:

  • Documented every public SAML URI/algorithm/status constant in Constants.java.
  • Added leading main descriptions to getters/setters and builder methods that previously had only @param/@return tags.
  • Documented exception classes, their error-code constants and constructors.
  • Filled in empty @param/@return descriptions and the missing @param <T> / @param statusXpath tags.

No behavior, method signatures or constant values were changed. A few explicit empty no-arg constructors were added solely to satisfy doclint's "use of default constructor" warning; they are behaviorally identical to the implicit defaults.

Verified: mvn clean javadoc:javadoc now reports BUILD SUCCESS with zero warning: and zero error: lines, and mvn clean compile succeeds.

Add missing Javadoc comments and main descriptions across core and toolkit
modules so that 'mvn clean javadoc:javadoc' completes with zero warnings.

- Document all public SAML URI/constant values in Constants.java
- Add main descriptions to getters/setters and builder methods
- Document exception classes, error-code constants and constructors
- Fill in empty @param/@return tags and missing type-param docs

Only Javadoc was changed; no behavior, signatures or constant values
were modified. A few explicit empty no-arg constructors were added solely
to satisfy doclint's default-constructor warning (behavior unchanged).
@marevol marevol merged commit 3eabc4a into main Jun 13, 2026
1 check passed
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.

1 participant