Skip to content
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 pmd.api.version from 7.2.0 to 7.3.0 #1074

Merged
merged 1 commit into from
Jul 2, 2024

Bump pmd.api.version from 7.2.0 to 7.3.0

a47762f
Select commit
Loading
Failed to load commit list.
Merged

Bump pmd.api.version from 7.2.0 to 7.3.0 #1074

Bump pmd.api.version from 7.2.0 to 7.3.0
a47762f
Select commit
Loading
Failed to load commit list.
ci.jenkins.io / Maven succeeded Jul 1, 2024 in 0s

85 new issues, 94 total

Total New Outstanding Fixed Trend
94 85 9 0 πŸ‘Ž

Reference build: Plugins Β» analysis-model Β» main #220

Details

Severity distribution of new issues

Error Warning High Warning Normal Warning Low
0 0 85 0

Annotations

Check warning on line 3845 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Issue.java:[519,12] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3848 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Issue.java:[560,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3851 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Issue.java:[727,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3854 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Issue.java:[756,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3857 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Issue.java:[863,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3860 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Severity.java:[121,28] [PreferredInterfaceType] Method return type can use a more specific type to convey more information to callers.</code></pre>

Check warning on line 3863 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Severity.java:[124,12] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3866 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Severity.java:[127,17] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3869 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Severity.java:[131,17] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3872 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Severity.java:[198,17] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3875 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\FileNameResolver.java:[66,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3878 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1304,22] [PreferredInterfaceType] Variable type can use a more specific type to convey more information to callers.</code></pre>

Check warning on line 3881 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1283,32] [PreferredInterfaceType] Variable type can use a more specific type to convey more information to callers.</code></pre>

Check warning on line 3884 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1284,32] [PreferredInterfaceType] Variable type can use a more specific type to convey more information to callers.</code></pre>

Check warning on line 3887 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[162,16] [YodaCondition] The non-constant portion of an equals check generally comes first. Prefer e.equals(CONSTANT) if e is non-null or Objects.equals(e, CONSTANT) if e may be</code></pre>

Check warning on line 3890 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[262,18] [CanIgnoreReturnValueSuggester] Methods that always return &#x27;this&#x27; (or return an input parameter) should be annotated with @com.google.errorprone.annotations.CanIgnoreReturnValue</code></pre>

Check warning on line 3893 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[289,18] [CanIgnoreReturnValueSuggester] Methods that always return &#x27;this&#x27; (or return an input parameter) should be annotated with @com.google.errorprone.annotations.CanIgnoreReturnValue</code></pre>

Check warning on line 3896 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[308,18] [CanIgnoreReturnValueSuggester] Methods that always return &#x27;this&#x27; (or return an input parameter) should be annotated with @com.google.errorprone.annotations.CanIgnoreReturnValue</code></pre>

Check warning on line 3899 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[325,18] [CanIgnoreReturnValueSuggester] Methods that always return &#x27;this&#x27; (or return an input parameter) should be annotated with @com.google.errorprone.annotations.CanIgnoreReturnValue</code></pre>

Check warning on line 3902 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[843,35] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3905 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[855,15] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3908 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[887,15] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3911 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1003,15] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3914 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1115,19] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>

Check warning on line 3917 in jenkins-console.log

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / Maven

spotbugs:spotbugs

NORMAL:
Raw output
<pre><code>C:\Jenkins\agent\workspace\Plugins_analysis-model_PR-1074\src\main\java\edu\hm\hafner\analysis\Report.java:[1123,32] [Varifier] Consider using `var` here to avoid boilerplate.</code></pre>