KnowForge/Google Guice
Releases

Guice 6.0.0

qianmoQqianmoQ· 更新于 2026-09-23· 阅读 25 分钟· 0 次阅读
登录后可跨设备保存划线和私人笔记登录

Guice 6.0.0

Released May 12th, 2023.

Maven

Guice:

<dependency>
  <groupId>com.google.inject</groupId>
  <artifactId>guice</artifactId>
  <version>6.0.0</version>
</dependency>

Extensions:

<dependency>
  <groupId>com.google.inject.extensions</groupId>
  <artifactId>guice-${extension}</artifactId>
  <version>6.0.0</version>
</dependency>

Downloads

Docs

Changes since Guice 5.1.0

JEE Jakarta Transition

Guice 6.0 adds support for jakarta.inject, the new namespace for the JSR330 spec (after the javax -> jakarta JEE transition). The following links talk more about the jakarta transition: Jarkata EE blog post, Eclipse Foundation blog post, Jakarta EE Wikipedia article, Oracle blog post

Guice 6.0 is being released alongside Guice 7.0 and is intended to help users migrate their code to the jakarta namespace. Guice 6.0 continues to fully support the javax.inject namespace while also mostly supporting the jakarta.inject namespace. The only part of Guice 6.0 that doesn't support jakarta.inject are the bind(..).toProvider methods. Those methods still require javax.inject or com.google.inject Providers.

The Guice 6.0 servlet & persist extensions only support the javax.servlet and javax.persistence namespaces respectively. If compatibility with jakarta.servlet or jakarta.persistence is required, use Guice 7.0.

Guice 7.0 removes support for javax.inject, javax.servlet and javax.persistence. Other than the namespace changes, Guice 6.0 & Guice 7.0 are identical.

Guice 6.0 can help with incremental migrations to the jakarta.inject namespace, by incrementally replacing javax.inject references to jakarta.inject. This works everywhere, except for code where a jakarta Provider is passed to bind(..).toProvider. Any one of the following options can be used to workaround the toProvider issue.

  1. Update to Guice 7.0 instead. Guice 7.0 fully supports jakarta.inject (but does not have support for javax.inject anymore).
  2. Change the provider implementation to instead implement com.google.inject.Provider (which works in both 6.0 & 7.0).
  3. Change the provider implementations to instead be @Provides methods, or add a wrapper @Provides method that delegates to the actual provider.
  4. Call bind(..).toProvider(Providers.guicify(myJakartaProvider)). The guicify method will adapt a jakarta provider instance to a com.google.inject.Provider. This only works if binding a Provider instance. It will not work for binding provider classes, type literals, or keys. If using this approach, it's best to revert the guicify calls when later updating to Guice 7.0, because they otherwise mask the actual provider implementation (which can be accessed through the Guice SPI's ProviderInstanceBinding.getUserSuppliedProvider).

Note that even though Guice 6.0's toProvider methods don't support jakarta providers, Guice 6.0 can inject jakarta.inject.Provider.

Details

See https://github.com/google/guice/compare/5.1.0...6.0.0 for a complete list of changes.

Guice Core

Servlet

Persist

Persist had a number of changes, some of which are backwards incompatible. Notably: injection of EntityManager no longer implicitly starts a unit of work (because this led to leaks). Users can opt-in to the legacy behavior by constructing the JpaPersistModule with a JpaPersistOptions that sets setAutoBeginWorkOnEntityManagerCreation to true.

评论

登录后参与评论

正在加载评论…