-
```
This is the specific example that bit us. There may be a more general case to
be found.
The visibility modifiers (or lack thereof) on A and B are important.
---
package x;
public class A {
…
-
```
This is the specific example that bit us. There may be a more general case to
be found.
The visibility modifiers (or lack thereof) on A and B are important.
---
package x;
public class A {
…
-
```
This is the specific example that bit us. There may be a more general case to
be found.
The visibility modifiers (or lack thereof) on A and B are important.
---
package x;
public class A {
…
-
```
This is the specific example that bit us. There may be a more general case to
be found.
The visibility modifiers (or lack thereof) on A and B are important.
---
package x;
public class A {
…
-
```
What steps will reproduce the problem?
According to the Guice injection points document at:
https://github.com/google/guice/wiki/InjectionPoints
injection methods of super classes are called befo…
-
```
What steps will reproduce the problem?
According to the Guice injection points document at:
https://github.com/google/guice/wiki/InjectionPoints
injection methods of super classes are called befo…
-
```
What steps will reproduce the problem?
According to the Guice injection points document at:
https://github.com/google/guice/wiki/InjectionPoints
injection methods of super classes are called befo…
-
```
What steps will reproduce the problem?
According to the Guice injection points document at:
https://github.com/google/guice/wiki/InjectionPoints
injection methods of super classes are called befo…
-
```
What steps will reproduce the problem?
1. add to a GIN-managed class a method like:
@Inject(optional = true) void injectA(A object){ }
, where A is a class not configured anywhere in GIN modules
…
-
```
What steps will reproduce the problem?
1. add to a GIN-managed class a method like:
@Inject(optional = true) void injectA(A object){ }
, where A is a class not configured anywhere in GIN modules
…