dagger-2

Has anyone used Lombok 1.16 with Dagger2? My current code looks like: @AllArgsConstructor(onConstructor = @__(@Inject)) public class JuiceMaker { private final Apple apple; The error is: JuiceMaker cannot be provided without an @Inject constructor or from an @Provides-annotated method. Without the Lombok annotation this actually works, so: public class JuiceMaker { private final Apple apple; @Inject public JuiceMaker(Apple apple){ this.apple = apple } } works This is a copy paste version of my answer here : This is not a direct answer to the question, which seems to be solved, but acts as

I have two classes, Foo<T> and Bar , which depend on each other, as well as various other classes. I am using Dagger-2 for dependency injection, but if I naively add the circular dependency, Dagger hits a stack overflow at runtime. What's a good way to refactor the classes to fix this, while still using Dagger to inject all the other dependencies, and with minimal duplication and changes to existing calls? The easy way out is to use Lazy<T> on one side. Lazy<Foo> foo; @Inject Bar(Lazy<Foo> foo) { this.foo = foo; } // use foo.get(); when needed After an excessive amount of thought and talks

I've got a strange problem here, and I'm not quite sure why what I'm doing isn't allowed. I've got the following modules: @Module public final class AppModule { private Context mContext; @Provides @Singleton @AppContext public Context provideContext() { return mContext; } } @Module public final class NetModule { @Provides @Singleton public OkHttpClient provideOkHttp() { return new OkHttpClient.Builder().build(); } } For various reasons, I don't want to have these two modules in the same component (basically due to my project structure). So I tried to create the following components: @Singleton

At this point, my understanding of Dependency Injection (DI) is only from this article . I'm interested to try, but I just need to clarify some things: Many refer DI as a tool to reduce boilerplate code. But according to that tutorial, the setup of Dagger 2 tends to create even more classes for configuration (module and component). I have not tried it, but by the looks of it, it isn't reducing the code, it is just splitting them so the main class can look tidier. Am I wrong on this one? Despite Dagger 2's claim that DI isn't just for testing, many are regarding its usage mainly for testing,

I've recently started using dagger-2 with kotlin. Unfortunately I have ecnountered a problem with sumbcomponants and I have trouble understanding why I get this gradle error: ...NetComponent (unscoped) may not reference scoped bindings: @dagger.Subcomponent(modules = {com.example.kremik.cryptodroid.di.module.NetModule.class}) @Singleton @Provides com.example.kremik.cryptodroid.data.remote.CMCService com.example.kremik.cryptodroid.di.module.NetModule.providesCMCService(retrofit2.Retrofit) @Singleton @Provides retrofit2.Retrofit com.example.kremik.cryptodroid.di.module.NetModule.providesRetrofit

I just started doing dependency injection using Dagger 2 . When I spun up my modules , components and tried to build my application, gradle threw the error Error:(4, 24) error: cannot find symbol class Generated I dug into it and found that the error is in one of the classes Dagger generates to do DI . The particular class that's missing was javax.annotation.Generated and the line throwing the error is the line that anntotates a Dagger generated class as @Generated("dagger.internal.codegen.ComponentProcessor") This question helped in finding the solution which is to add the javax package as a