Skip to content

Use Palantir Java Format 2.73.0 #702

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

MarkEWaite
Copy link
Contributor

@MarkEWaite MarkEWaite commented Aug 8, 2025

Use Palantir Java Format 2.73.0

Palantir Java Format 2.73.0 was released last week.

The git client plugin use of spotless needs the Palantir Java Format upgrade to 2.73.0 in order to run spotless with Java 25.

The Palantir Java Format upgrade does not seem to be required for Jenkins core to run spotless with Java 25. This will keep the core pom version of Palantir Java Format consistent with the version needed in the plugin pom.

Matching pull request submitted to plugin pom:

Testing done

Confirmed that mvn spotless:apply succeeds with Java 25 EA build 28 on Jenkins core with or without this change.

Confirmed that mvn spotless:apply makes no formatting changes in Jenkins core with this change.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

https://github.com/palantir/palantir-java-format/releases/tag/2.73.0
shows it was released last week.

The git client plugin use of `spotless` needs the Palantir Java Format
upgrade to 2.73.0 in order to run `spotless` with Java 25.  The Palantir
Java Format upgrade does not seem to be required for Jenkins core to run
`spotless` with Java 25.

Testing done:

Confirmed that `mvn spotless:apply` succeeds with Java 25 EA build 28
on Jenkins core with or without this change.

Confirmed that `mvn spotless:apply` makes no formatting changes in
Jenkins core with this change.
MarkEWaite added a commit to MarkEWaite/plugin-pom that referenced this pull request Aug 8, 2025
https://github.com/palantir/palantir-java-format/releases/tag/2.73.0
shows it was released last week.

The git client plugin use of `spotless` needs the Palantir Java Format
upgrade to 2.73.0 in order to run `spotless` with Java 25.  The Palantir
Java Format upgrade does not seem to be required for Jenkins core to run
`spotless` with Java 25.

Matching pull request in the core pom:

* jenkinsci/pom#702

Testing done:

Confirmed that `mvn spotless:apply` fails with Java 25 EA build 28 on
git client plugin without this change.

Confirmed that `mvn spotless:apply` succeeds with Java 25 EA build 28
on git client plugin with this change.

Confirmed that `mvn spotless:apply` makes no formatting changes in git
client plugin with this change.
MarkEWaite added a commit to jenkinsci/plugin-pom that referenced this pull request Aug 8, 2025
https://github.com/palantir/palantir-java-format/releases/tag/2.73.0
shows it was released last week.

The git client plugin use of `spotless` needs the Palantir Java Format
upgrade to 2.73.0 in order to run `spotless` with Java 25.  The Palantir
Java Format upgrade does not seem to be required for Jenkins core to run
`spotless` with Java 25.

Matching pull request in the core pom:

* jenkinsci/pom#702

Testing done:

Confirmed that `mvn spotless:apply` fails with Java 25 EA build 28 on
git client plugin without this change.

Confirmed that `mvn spotless:apply` succeeds with Java 25 EA build 28
on git client plugin with this change.

Confirmed that `mvn spotless:apply` makes no formatting changes in git
client plugin with this change.
@MarkEWaite MarkEWaite merged commit ddb38d1 into jenkinsci:master Aug 8, 2025
2 checks passed
@MarkEWaite MarkEWaite deleted the use-palantir-formatter-2.73.0 branch August 8, 2025 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants