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

Fix some gradle configuration #247

Merged
merged 7 commits into from
Jan 10, 2024
Merged

Fix some gradle configuration #247

merged 7 commits into from
Jan 10, 2024

Conversation

slinkydeveloper
Copy link
Collaborator

@slinkydeveloper slinkydeveloper commented Jan 9, 2024

A bunch of fixes for the gradle configuration, including fix #237 (first commit)

build.gradle.kts Outdated
Comment on lines 78 to 85
java { toolchain { languageVersion = JavaLanguageVersion.of(11) } }
java {
sourceCompatibility = JavaVersion.VERSION_17
targetCompatibility = JavaVersion.VERSION_17
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This toolchain thing fixes to a specific java version, which causes #237. Using source/target compatibility should work with any sdk version >= 17

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I tried now to enable the auto jvm download in the last commit, it sounds like a useful feature. I wonder though if it works on NixOS, perhaps @igalshilman give this a try to see if your machine likes it :)

Copy link
Contributor

Choose a reason for hiding this comment

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

works like magic 🪄

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Amazing!

Copy link
Contributor

Choose a reason for hiding this comment

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

I can confirm that it works on my machine as well. Thanks @slinkydeveloper for working your magic on this ❤️

Copy link

github-actions bot commented Jan 9, 2024

Test Results

102 files  ±0  102 suites  ±0   10m 8s ⏱️ -11s
 93 tests ±0   93 ✅ ±0  0 💤 ±0  0 ❌ ±0 
232 runs  ±0  232 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 80d88fc. ± Comparison against base commit 082e023.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

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

Thanks a lot for improving our e2e tests @slinkydeveloper. I think it is a really good improvement. I've tested them locally and it seems to work :-) +1 for merging.

Comment on lines +149 to +154
check {
dependsOn(testAlwaysSuspending)
dependsOn(testSingleThreadSinglePartition)
dependsOn(testPersistedTimers)
dependsOn(testLazyState)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice, really cool. Now it is actually possible to run individually tests via --tests. I think this is now also possible because you've removed the explicit TestReport task. Really good! I guess we can then also close #115.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I didn't notice that I fixed that as well 🤣

@slinkydeveloper slinkydeveloper merged commit 82d548b into main Jan 10, 2024
2 checks passed
@slinkydeveloper slinkydeveloper deleted the fix-gradle branch January 10, 2024 17:06
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.

build.gradle.kts requires explicitly java11
4 participants