Bumped Guice to 5.1.0 to add Java 17 compatibility#1405
Open
krahl wants to merge 1 commit intobwssytems:masterfrom
Open
Bumped Guice to 5.1.0 to add Java 17 compatibility#1405krahl wants to merge 1 commit intobwssytems:masterfrom
krahl wants to merge 1 commit intobwssytems:masterfrom
Conversation
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When LinuxServer.io bumped their ha-bridge container to Java 17 in linuxserver/docker-habridge#23 I noticed that ha-bridge isn't yet Java 17 compatibile. This mainly stems from the shaded cglib in Guice 4.1.0. Google published Guice 5.1.0 a while ago which removes cglib and adds official Java 17 support.
A quick smoke test with a ha-bridge jar using Guice 5.1.0 seems to run fine with Java 17 and works with Harmony, REST calls and MQTT integration