Skip to content

Get rid of JVM specific default palantir formatter version #2685

@kwin

Description

@kwin

In

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions