fix: resolve Javadoc warnings - #13
Merged
Merged
Conversation
Add a class-level Javadoc description and an explicit documented no-arg constructor to OgnlEngine to eliminate the "no comment" and "use of default constructor" Javadoc warnings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves the 2 Javadoc warnings reported by
mvn clean javadoc:javadocinOgnlEngine:no commenton theOgnlEngineclass -> added a concise class-level description.use of default constructor, which does not provide a comment-> added an explicit, documented public no-arg constructor.Verification:
mvn clean javadoc:javadocnow reports BUILD SUCCESS with zerowarning:and zeroerror:lines from the javadoc tool. Only Javadoc comments and an explicit constructor were touched; no behavior changes.