-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0 #869
Bump com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0 #869
Conversation
57807f1
to
8967554
Compare
Bumps [com.github.spotbugs:spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.7.3.6 to 4.8.2.0. - [Release notes](https://github.com/spotbugs/spotbugs-maven-plugin/releases) - [Commits](spotbugs/spotbugs-maven-plugin@spotbugs-maven-plugin-4.7.3.6...spotbugs-maven-plugin-4.8.2.0) --- updated-dependencies: - dependency-name: com.github.spotbugs:spotbugs-maven-plugin dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
8967554
to
a4dd7e9
Compare
Does #859 (review) still apply? Were there new false positives that were particularly problematic? https://github.com/spotbugs/spotbugs/releases/tag/4.8.2 |
Jenkins CLI reports two new spotbugs warnings with spotbugs 4.8.2:
When I suppress those two spotbugs warnings with a suppression in the source file, then the following additional spotbugs warnings appear:
|
The I guess we cannot exclude specific detectors at the POM level? Line 1018 in d1bd47d
ConstructorThrow to Line 120 in d1bd47d
(https://spotbugs.readthedocs.io/en/stable/bugDescriptions.html#pa-primitive-field-is-public-pa-public-primitive-attribute seems a reasonable warning in general; for a |
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
From jenkinsci/plugin-pom#869 (comment) > Discussion in spotbugs/spotbugs#2695 > https://wiki.sei.cmu.edu/confluence/display/java/OBJ11-J.+Be+wary+of+letting+constructors+throw+exceptions > seems to relate to libraries used with SecurityManager which is dead > and certainly does not apply to Jenkins; we do not expect untrusted code > to be running inside the controller JVM, and it does not seem plausible > that finalizer abuse would happen by accident.
Suppress the CT_CONSTRUCTUR_THROWS warning because it is not helpful in a Jenkins context. jenkinsci/plugin-pom#869 (comment) gives more details.
Suppress the CT_CONSTRUCTUR_THROWS warning because it is not helpful in a Jenkins context. jenkinsci/plugin-pom#869 (comment) gives more details.
jenkinsci/pom#510 needs this change along with checks of the other repositories that use the Jenkins parent pom. jenkinsci/pom#501 (review) recommends that the new spotbugs issues be either suppressed or resolved in the upstream release of spotbugs. This change suppresses the new warning for primitive fields that are pu9blicly visible and the new warning for a few cases where a field could be made static. This change skips the warnings related to CT_CONSTRUCTOR_THROWS because they are not relevant to Jenkins. jenkinsci/plugin-pom#869 (comment) provides more details along with the discussion at spotbugs/spotbugs#2695
The CT_CONSTRUCTOR_THROW bug pattern is related to libraries used with SecurityManager and does not apply to Jenkins; we do not expect untrusted code to be running inside the controller JVM, therefore we suppress it globally. jenkinsci/plugin-pom#869 (comment) has more details.
jenkinsci/pom#510 needs this change along with checks of the other repositories that use the Jenkins parent pom. jenkinsci/pom#501 (review) recommends that the new spotbugs issues be either suppressed or resolved in the upstream release of spotbugs. This change suppresses the new warning for primitive fields that are pu9blicly visible and the new warning for a few cases where a field could be made static. This change skips the warnings related to CT_CONSTRUCTOR_THROWS because they are not relevant to Jenkins. jenkinsci/plugin-pom#869 (comment) provides more details along with the discussion at spotbugs/spotbugs#2695
…ugs-maven-plugin-4.8.2.0
The CT_CONSTRUCTOR_THROW bug pattern is related to libraries used with SecurityManager and does not apply to Jenkins; we do not expect untrusted code to be running inside the controller JVM, therefore we suppress it globally. #869 (comment) has more details
Thanks for approving the pull request @jglick . I'd like to first merge and release the parent pom pull request that is used for Jenkins core and watch it through the process of updating the repositories that depend on it. That may expose other changes that we need to make before this is merged and released. Does that seem OK to you? Would you be willing to review and approve the Jenkins core parent pom pull request: |
Whatever you think makes sense. I do not have much to add. |
The CT_CONSTRUCTOR_THROW bug pattern is related to libraries used with SecurityManager and does not apply to Jenkins; we do not expect untrusted code to be running inside the controller JVM, therefore we suppress it globally. jenkinsci/plugin-pom#869 (comment) has more details.
A newer version of com.github.spotbugs:spotbugs-maven-plugin exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
jenkinsci/plugin-pom#869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later. Plugin pom 4.77 is likely to include that new version of spotbugs.
jenkinsci/plugin-pom#869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later. Plugin pom 4.77 is likely to include that new version of spotbugs.
jenkinsci/plugin-pom#869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later. Plugin pom 4.77 is likely to include that new version of spotbugs. Confirmed that the spotbugs warnings are visible when using the 4.77-SNAPSHOT plugin pom before this change. With this change, the spotbugs warnings are no longer visible.
@dependabot recreate |
Superseded by #884. |
jenkinsci/plugin-pom#869 or a subsequent pull request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later. Plugin pom 4.77 is likely to include that new version of spotbugs.
request that updates to 4.8.3 will need this change in the plugin to resolve new spotbugs warnings that will be reported by spotbugs 4.8.2 and later. Plugin pom 4.77 is likely to include that new version of spotbugs. Confirmed that the spotbugs warnings are visible when using the 4.77-SNAPSHOT plugin pom before this change. With this change, the spotbugs warnings are no longer visible.
Bumps com.github.spotbugs:spotbugs-maven-plugin from 4.7.3.6 to 4.8.2.0.
Release notes
Sourced from com.github.spotbugs:spotbugs-maven-plugin's releases.
... (truncated)
Commits
4737e86
[maven-release-plugin] prepare release spotbugs-maven-plugin-4.8.2.06052ca1
[pom] Sort order of maven reporting api/impl4ed4adc
Merge pull request #687 from hazendaz/master8b483fc
[pom] Remove clean goal from invoker as its never existed7ef8b3a
Merge pull request #686 from hazendaz/master2f28d9c
[GHA] For maven wrapper downloads, just use maven there to do that instead of...c0b13b8
Merge pull request #684 from spotbugs/renovate/maven-3.x1df4aad
Merge pull request #685 from spotbugs/renovate/mavenversiondb1181d
Update mavenVersion to v3.9.622ff278
Update dependency maven to v3.9.6You can trigger a rebase of this PR by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)