Skip to content

Bump org.jvnet.hudson.plugins:analysis-pom from 10.11.0 to 10.12.0

cefef0e
Select commit
Loading
Failed to load commit list.
Closed

Bump org.jvnet.hudson.plugins:analysis-pom from 10.11.0 to 10.12.0 #1010

Bump org.jvnet.hudson.plugins:analysis-pom from 10.11.0 to 10.12.0
cefef0e
Select commit
Loading
Failed to load commit list.
ci.jenkins.io / PMD failed Jul 2, 2025 in 0s

9 new issues

Total New Outstanding Fixed Trend
9 9 0 0 👎

Reference build: Plugins » git-forensics-plugin » main #227

Details

Severity distribution of new issues

Error Warning High Warning Normal Warning Low
0 0 9 0

Annotations

Check warning on line 126 in plugin/src/main/java/io/jenkins/plugins/forensics/git/blame/GitBlamer.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD.UseTryWithResources" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 41 in plugin/src/main/java/io/jenkins/plugins/forensics/git/delta/DeltaRepositoryCallback.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 60 in plugin/src/main/java/io/jenkins/plugins/forensics/git/miner/CommitStatisticsStep.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD.ExcessiveImports" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 25 in plugin/src/main/java/io/jenkins/plugins/forensics/git/reference/GitReferenceRecorder.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 16 in plugin/target/generated-sources/localizer/io/jenkins/plugins/forensics/git/reference/Messages.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 44 in plugin/src/test/java/io/jenkins/plugins/forensics/git/blame/GitBlamerTest.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD.ExcessiveImports" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 23 in plugin/src/test/java/io/jenkins/plugins/forensics/git/reference/GitCheckoutListenerITest.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 52 in plugin/src/test/java/io/jenkins/plugins/forensics/git/reference/GitReferenceRecorderITest.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD.GodClass" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>

Check warning on line 46 in plugin/src/test/java/io/jenkins/plugins/forensics/git/util/GitITest.java

See this annotation in the file changed.

@ci-jenkins-io ci-jenkins-io / PMD

UnnecessaryWarningSuppression

NORMAL:
Unnecessary suppression "PMD.SignatureDeclareThrowsException" in @SuppressWarnings annotation.
Raw output
This rule reports suppression comments and annotations that did not suppress any PMD violation. Note that violations of this rule cannot be suppressed. Please note: - The rule will report those suppressions comments/annotations that did not suppress a violation _during the current run_. That means you cannot run this rule separately from other rules, it must always be run with all the rules that could produce a warning. This is most likely not a problem, as you can just include this rule in your regular ruleset. - The rule for now only reports annotations specific to PMD, like `@SuppressWarnings("PMD")`. For instance `@SuppressWarnings("all")` is never reported as we cannot know if another tool is producing a warning there that must be suppressed. In the future we might be able to check for other common ones like `@SuppressWarnings("unchecked")` or `"fallthrough"`. <pre> <code> public class Something { // Unless some rule triggered on the following line, this rule will report the comment: private void foo() {} // NOPMD } </code> </pre> <a href="https://docs.pmd-code.org/pmd-doc-7.14.0/pmd_rules_java_bestpractices.html#unnecessarywarningsuppression"> See PMD documentation. </a>