Make Beam expansion service shadowJar multi-release#33472
Make Beam expansion service shadowJar multi-release#33472Abacn merged 1 commit intoapache:masterfrom
Conversation
…ulti-release dependencies correctly
94f3e01 to
4db5b67
Compare
kennknowles
left a comment
There was a problem hiding this comment.
This matches the fix I had to do in some other places. Did it work for this jar? Perhaps we should make it default somehow... I don't know if there is a downside.
|
Yeah I think it's working. To test, Creating a gradle project: with a main class: Run with Java 21. Before (run on nightly): After: |
yeah I made it default to expansion services, where technically is run on different jre environment, and directly (without dependency resolution like maven or gradle) Did a little search it seems multi-release jar is a debated, e.g. this blog https://blog.gradle.org/mrjars . So I ended up with only enabling it if upstream dependencies has used multi-released jar imo the issue itself kind of indicated multi-release jar can bring problems. |
Good point. And thanks for the link to that article. It does seem like this could have the same impact on Beam users who build fat jars. |
…ease branch (Make Beam expansion service shadowJar multi-release)
…ulti-release dependencies correctly (apache#33472)
so it processes multi-release dependencies correctly
Fix #33471
Please add a meaningful description for your change here
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>instead.CHANGES.mdwith noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.