[WIP] Replace the usage of commons-beanutils with spring-beans #711
ci.jenkins.io / SpotBugs
failed
Aug 27, 2025
2 new issues
| Total | New | Outstanding | Fixed | Trend |
|---|---|---|---|---|
| 2 | 2 | 0 | 0 | 👎 |
Reference build: Core » stapler » master #377
Details
Severity distribution of new issues
| Error | Warning High | Warning Normal | Warning Low |
|---|---|---|---|
| 0 | 0 | 2 | 0 |
Annotations
Check warning on line 1209 in core/src/main/java/org/kohsuke/stapler/RequestImpl.java
ci-jenkins-io / SpotBugs
DE_MIGHT_IGNORE
NORMAL:
org.kohsuke.stapler.RequestImpl.copyProperty(Object, String, Object) might ignore java.lang.Exception
Raw output
<p> This method might ignore an exception. In general, exceptions should be handled or reported in some way, or they should be thrown out of the method.</p>
Check warning on line 1209 in core/src/main/java/org/kohsuke/stapler/RequestImpl.java
ci-jenkins-io / SpotBugs
REC_CATCH_EXCEPTION
NORMAL:
Exception is caught when Exception is not thrown in org.kohsuke.stapler.RequestImpl.copyProperty(Object, String, Object)
Raw output
<p> This method uses a try-catch block that catches Exception objects, but Exception is not thrown within the try block, and RuntimeException is not explicitly caught. It is a common bug pattern to say try { ... } catch (Exception e) { something } as a shorthand for catching a number of types of exception each of whose catch blocks is identical, but this construct also accidentally catches RuntimeException as well, masking potential bugs. </p> <p>A better approach is to either explicitly catch the specific exceptions that are thrown, or to explicitly catch RuntimeException exception, rethrow it, and then catch all non-Runtime Exceptions, as shown below:</p> <pre><code>try { ... } catch (RuntimeException e) { throw e; } catch (Exception e) { ... deal with all non-runtime exceptions ... } </code></pre>
Loading