Get rid of JVM specific default palantir formatter version

In

spotless/lib/src/main/java/com/diffplug/spotless/java/PalantirJavaFormatStep.java

Line 32 in 6f1919f

    
           private static final Jvm.Support<String> JVM_SUPPORT = Jvm.<String> support(NAME).add(8, "1.1.0").add(11, "2.28.0").add(21, "2.57.0");

the default version of palantir is determined based on the current Java version.

That is not necessary as latest spotless requires Java 17 and palantir-java-format (even in the newest version) is runnable on Java 11+. For details refer to #2451 (comment).

So it should be safe to pick 2.80.0 for all Java versions right now. This solves issues like #2625 or #2503 at least for palantir.

@nedtwigg

@nedtwigg Any idea why 2.74.0 was only deemed compatible with Java 21+ (

spotless/lib/src/main/java/com/diffplug/spotless/java/PalantirJavaFormatStep.java

Line 38 in 036c0b0

    
           private static final Jvm.Support<String> JVM_SUPPORT = Jvm.<String> support(NAME).add(8, "1.1.0").add(11, "2.28.0").add(21, "2.71.0");

)?

i'm not sure of the history here, happy to merge something that does .add(8, "1.1.0").add(11, "2.80.0")

Why do you think you need something for java 8 given that spotless requires 17?

Ah, good point! I suppose we can remove it entirely.

Get rid of Java-specific default Palantir version

Get rid of Java-specific default Palantir version (#2686 fixes #2685)

Navigation Menu

Repository navigation

Get rid of JVM specific default palantir formatter version #2685

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Get rid of JVM specific default palantir formatter version #2685

Description

Activity

kwin commented on Oct 15, 2025

nedtwigg commented on Oct 15, 2025

kwin commented on Oct 15, 2025

nedtwigg commented on Oct 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions