-
```
Having both is certainly cause for confusion. We should canonicalize these,
such that a binding for
one can be used to inject the other.
```
Original issue reported on code.google.com by `limpb…
-
```
Since com.google.inject.util.Providers adds support for javax.inject.Provider,
I wonder why there's not anything to support javax.inject.Named.
One quick way could be the com.google.inject.name.…
-
```
Having both is certainly cause for confusion. We should canonicalize these,
such that a binding for
one can be used to inject the other.
```
Original issue reported on code.google.com by `limpb…
-
```
Since com.google.inject.util.Providers adds support for javax.inject.Provider,
I wonder why there's not anything to support javax.inject.Named.
One quick way could be the com.google.inject.name.…
-
```
Since com.google.inject.util.Providers adds support for javax.inject.Provider,
I wonder why there's not anything to support javax.inject.Named.
One quick way could be the com.google.inject.name.…
-
```
Since com.google.inject.util.Providers adds support for javax.inject.Provider,
I wonder why there's not anything to support javax.inject.Named.
One quick way could be the com.google.inject.name.…
-
The issue is with the init method in the SpringPluginManager class.
The method is annotated by javax.annotation.PostConstruct which is deprecated and replaced by jakarta.annotation.PostConstruct.
Th…
-
When developing plugins/extensions it is often required to annotate constructors, etc with `@Inject`. At the moment, Gradle only respects `javax.inject.Inject`. However, `javax.inject.Inject` has be…
-
Program type already present: javax.inject.Inject
Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
-
```
Supposing to deal with JSR330 Providers, we cannot write:
class MyProvider implements javax.inject.Provider {}
binder.bind(...).toProvider(new MyProvider(...));
since toProvider only accepts Gui…