Fix UWF_NULL_FIELD in DescriptorGeneratorMojo by initializing mojoDependencies #1028
Conversation
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
MateusJunior7
force-pushed
the
fix-uwf-mojoDependencies
branch
from
b57f17e to
4e82276
Compare
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.
This PR fixes a UWF_NULL_FIELD warning reported by SpotBugs in org.apache.maven.plugin.plugin.DescriptorGeneratorMojo.
The field mojoDependencies was declared but never initialized, which left it in a null state.
It is now initialized as an empty ArrayList, removing the null-only assignment and improving robustness.
After this change, the UWF_NULL_FIELD warning is no longer reported for this class
(maven-plugin-plugin module builds successfully and SpotBugs reports are clean for this issue).