Skip to content
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

Add Java version - see guardian/gha-scala-library-release-workflow#36 #139

Merged
merged 1 commit into from
May 21, 2024

Conversation

rtyley
Copy link
Member

@rtyley rtyley commented May 20, 2024

See guardian/gha-scala-library-release-workflow#36 - gha-scala-library-release-workflow has moved to requiring projects to specify what version of Java they want to use to build, and this is expressed through an asdf-formatted .tool-versions file.

This allows individual projects to experiment with later (or even earlier) versions of Java if they wish, without requiring all other projects using gha-scala-library-release-workflow to upgrade their version of Java at the same time.

"But maybe we need to support older versions of Java!"

Note that, although this PR specifies Java 21 (the latest LTS release of Java, which apparently has several performance benefits) for the library build, the artifacts released by the project do not need to require Java 21 - so long as the scalacOptions defined in the project's build.sbt includes a -release flag, we can specify that we want the artifacts to support some older version of Java (eg -release:11 for Java 11).

@rtyley rtyley requested a review from a team as a code owner May 20, 2024 10:22
Copy link
Contributor

@twrichards twrichards left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks @rtyley

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants