Guice dead (EOL)?

[c-stachow]

Since 2 years no release has been created although there is commit activity.
I am concerned since #1822 is open for over 1 year and it looked like it requires compile changes to upgrade the dependency. So this dependency will be unusable in a foreseeable time.
When will there be a new release?

[sheinbergon]

I would wait for JDK 25 LTS, They tend to release new versions around adding LTS version support

[wendigo]

@sheinbergon coincidence. There was never policy like that

[sheinbergon]

I agree, But the Java release policy and adaotion have also drastically changed in the past few years. As no one is answering the question - is this project EOL, I'd wait out the next LTS version release to see if the policy has unofficialy changed, before digging Guice's grave.

[Randgalt]

I guess this is the beauty of Apache. Projects at Apache tend to outlive their original authors.

[Randgalt]

There is the example of Java Poet. https://github.com/square/javapoet. Another company took over stewardship of it. https://github.com/palantir/javapoet. I started a fork but it's too much of a burden to maintain. These things need to be at a company level unless some individual (or group) is very motivated.

[adolfojunior]

Can I say it's dead? 🪦🪦🪦

[bcmedeiros]

Created #1922 to track JDK 25 support specifically, let's upvote it and see how much traction it gets. It seems an important one if the project is still alive.

[GedMarc]

Considering the last merge to the branch was a week ago, and that guice powers the entirety of the java build ecosystem - pretty sure still going strong lol.

The fix for the JDK25 implementation is a two-liner, but when you have over 10k projects to test against for every change, I do imagine that yes it can take a bit.