My presumption is that there should be a way to do this automatically as part of the release process.

I'm not 100% how best to achieve this, so before running with it I'd like to open it out for discussion.

To start things off, this SO question has a few answers/suggestions.

One suggestio

Affects PMD Version:
All.

Rule:
ImmutableField

Description:

"Identifies private fields whose values never change once object initialization ends either in the declaration of the field or by a constructor. This helps in converting existing classes to becoming immutable ones."

Immutability, by defini

Inspired by comment spotbugs/spotbugs#797 (comment) on #797
implement a new detector which finds faulty regex patterns.

The detector should find faulty regexes in standard library methods
Pattern.compile(String regex)
Pattern.compile(String regex, int flags)
String.replaceFirst(String regex, String replacement)
String.replaceAll(String regex, String re

Description

The class ZipEntry describe one file inside a Zip archive. getName() return the file name from this file. It could contain a malicious string such as "../../../". If the value is used to build a file path, it could lead to a

inline templates:

• with anonymous classes
• with lambda

Expected Behavior

Each class should have it's own unit test

Actual Behavior

Not every class has it's own unit test

Steps to Reproduce the Problem

1. Look at the sources in src/main/java
2. Look for the same source file in src/test/java with Test appended to its name

Specifications

• n/a

When projects are very large, you might not want to enable automatic building or perform a full build on your project just to CheckStyle a single file you're working on.

With this preference enabled, saving the active document triggers a CheckStyle on it regardless of build settings. The result is you can rapidly re-check and fix CheckStyle issues rather than use the menu commands over and ove