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

Replace setup-scala with setup-java #6318

Merged
merged 3 commits into from
Feb 3, 2022
Merged

Conversation

mijicd
Copy link
Member

@mijicd mijicd commented Feb 2, 2022

Summary

  • replaces setup-scala with setup-java
  • sets Java 17 as default

@mijicd mijicd marked this pull request as ready for review February 3, 2022 06:24
Copy link
Member

@sideeffffect sideeffffect left a comment

Choose a reason for hiding this comment

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

IMHO we should keep JVM version 8 as the base version and use it everywhere. Other JVM versions, like 11 or 17 should be then tested only in the testJvms.

The motivation is that this will make sure that all things work on the widest range of JVM versions -- this is one of Scala's biggest strengths, it is a powerful language that you can run even on an "old" JVM 8.

@@ -99,15 +119,17 @@ jobs:
strategy:
fail-fast: false
matrix:
java: ['11', '17']
java: ['8', '11']
Copy link
Member

Choose a reason for hiding this comment

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

The purpose of the task testJvms is to test on other JVM versions besides the base one, so it should stay ['11', '17'].

Copy link
Member Author

@mijicd mijicd Feb 3, 2022

Choose a reason for hiding this comment

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

It should not, as the base one is now 17.

@mijicd
Copy link
Member Author

mijicd commented Feb 3, 2022

The motivation is that this will make sure that all things work on the widest range of JVM versions -- this is one of Scala's biggest strengths, it is a powerful language that you can run even on an "old" JVM 8.

If I'm not mistaken, that's the whole purpose behind the testJvms.

@mijicd mijicd merged commit 9f248be into zio:master Feb 3, 2022
@mijicd mijicd deleted the feature/upgrade-ci branch February 3, 2022 18:31
@mijicd
Copy link
Member Author

mijicd commented Feb 3, 2022

@adamgfraser Could you please sync the series/2.x branch?

@adamgfraser
Copy link
Contributor

@mijicd Will do!

@sideeffffect
Copy link
Member

sideeffffect commented Feb 3, 2022

If I'm not mistaken, that's the whole purpose behind the testJvms.

But how about the other actions, like lint, compile, publishLocal or website? Shouldn't we primarily test them on 8 (instead of 17)? 🤔

@mijicd
Copy link
Member Author

mijicd commented Feb 3, 2022

publishLocal and publish are still running on 8, due to the downward dependency. Regarding the other ones, I don't see that we're risking anything with migration to 17.

@sideeffffect
Copy link
Member

fair enough 👍

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.

None yet

4 participants