[STORM-3850] Static code analyzer (PMD) Errors

Repository metrics

Stars

6,517 stars (6,517 stars)

PR merge metrics

Avg merge 1d 10h (Avg merge 1d 10h)100 merged PRs in 30d (100 merged PRs in 30d)

Description

Contributor guide

Research direction

Find the PMD configuration (e.g., in pom.xml or a ruleset file), update the targetJdk to 1.8, then run the PMD analysis again. The new warnings will appear; fix each by refactoring the code to comply with PMD rules. Focus on methods using old constructs like explicit type declarations that can be replaced with diamond operator, or loops that can be enhanced.

Tech stack

java

Domain

backend

Issue type

Chore

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-2 days

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

JavaMavenGit

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65