-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to Dagger 2 #120
Comments
The Dagger 2 approach is significantly incompatible with Dagger 1, particularly as multiple components with singleton scopes are unsupported, as is overrides. It is probably better to remove dagger so that callers can choose dagger 1, dagger 2, spring, guice, etc. |
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 24, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 26, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 26, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. This change also drops support for javax.inject.Named, which has been replaced by feign.Param. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 26, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. This change also drops support for javax.inject.Named, which has been replaced by feign.Param. see #120
codefromthecrypt
pushed a commit
that referenced
this issue
Jan 26, 2015
Dagger 1.x and 2.x are incompatible. Rather than choose one over the other, this change removes Dagger completely. Users can now choose any injector, constructing Feign via its Builder. This change also drops support for javax.inject.Named, which has been replaced by feign.Param. see #120
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dagger 1.x is not likely to continue. Dagger 2 is.
I'm interested enough to help port everything here (and maybe fix some bugs etc along the way), plus revamp denominator accordingly.
Please ping this issue if you feel strongly that feign should not move to Dagger 2.
The text was updated successfully, but these errors were encountered: