arturobernalg opened a new pull request, #2210:
URL: https://github.com/apache/maven-resolver/pull/2210

   Adds missing descriptions, @param, @return and @throws tags across 
maven-resolver-api so that `mvn javadoc:javadoc` produces zero warnings under 
stricter JDK 25+ doclint. Fixes MRESOLVER-456.
   
   Claude-Session: https://claude.ai/code/session_01ReVkpYAznRPFBkHQFwYWcK
   
   ### What
   Adds the missing Javadoc content (descriptions, `@param`, `@return`, 
`@throws`) flagged by the javadoc tool's doclint when run under JDK 25/26, 
across all affected classes in `maven-resolver-api`.
   
   ### How
   - Added a one-sentence description to enum constants, interface/class 
members and constructors that lacked a main description.
   - Added missing `@param`, `@return` and `@throws` tags, matching the 
existing style and wording used elsewhere in the same file/interface (e.g. 
reusing `RepositoryListener`'s descriptions for the corresponding 
`RepositoryEvent.EventType` constants).
   - No behavioral changes; Javadoc-only.
   
   ### Tests
   - `JAVA_HOME=<jdk-26> mvn -pl maven-resolver-api clean javadoc:javadoc`: 0 
warnings (previously ~100 under JDK 25/26, reproducing the issue).
   - `mvn -pl maven-resolver-api test`: 91 tests, 0 failures.
   - `mvn -pl maven-resolver-api checkstyle:check`: 0 violations.
   
   ---
   
   To make clear that you license your contribution under
   the [Apache License Version 2.0, January 
2004](https://www.apache.org/licenses/LICENSE-2.0)
   check one of the following:
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [x] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to