-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UpgradeNextMajorParentVersion
produces code that SpotBug considers as errors
#748
Comments
When issuing this command:
When executed, the code gives a result file such as:
We could then add it to the
Could we create a recipe that does all that whenever we use a recipe that changes or upgrades the SpotBug version? 🤔 This process worked for this vmmanager-plugin PR. |
I tried this on this PR, and it allowed it to build. While it's not ideal to add exclusions to SpotBugs, it's something that can be done automatically. Unfortunately, we can't (as of today) automatically correct every flaw detected by SpotBugs. |
It looks like for Java 11, or the version of SpotBugs linked to Jenkins
which generated a |
Plugin Modernizer version
plugin modernizer 999999-SNAPSHOT (2025-01-29T09:30:07Z)
What Operating System are you using
Debian / WSL
Reproduction steps
java -jar plugin-modernizer-cli/target/jenkins-plugin-modernizer-999999-SNAPSHOT.jar run --plugins vmanager-plugin --recipe UpgradeNextMajorParentVersion
Detected error
The recipe produced the following PR: jenkinsci/vmanager-plugin#15 .
Expected Results
No error when compiling. 😉
Could this be outside the scope of this tool, or is it something the contributor should address before submitting their PR?
I initially assumed that the plugin-modernizer handled the compilation before creating the PR. Your insights would be greatly appreciated!
Don't get me wrong, I will fix these Spotbug-detected issues by myself, but, is that something the tool could take care of?
I doubt it. 🤔
Thanks for your help.
The text was updated successfully, but these errors were encountered: