No Dagger2 generated files for JUnit tests about dagger HOT 11 CLOSED

For me it works when adding dagger 2 with both apt and testCompile scopes.

BTW, it would be great if we could have an example of testing with Dagger 2. It's not obvious at all to figure out how module can be overiden.

from dagger.

Can you please provide an example project? I tried to add dagger compiler as a testCompile dependency but without success.

from dagger.

I'm also running into this issue. An example project or a few pointers would be helpful. Thanks!

from dagger.

That build.gradle script works for me (with android apt plugin):

dependencies {
    apt 'com.google.dagger:dagger-compiler:2.0-SNAPSHOT'
    compile 'com.google.dagger:dagger:2.0-SNAPSHOT'

    // Additional for unit tests
    testProvided 'com.google.dagger:dagger-compiler:2.0-SNAPSHOT'
}

from dagger.

Can you please provide an example project? I would like to see the whole project configuration related to JUnit tests.

from dagger.

Our recommendation for Android Studio is to use https://bitbucket.org/hvisser/android-apt as described above. I'm going to close this. If you are still encountering it when using the apt plugin, and after updating all dependencies, please re-open this, but point to either a github repo with an example project, or a gist containing a failing test, or something so we can reproduce this.

from dagger.

Here is the AndroidStudio example project: https://github.com/westward/Dagger2Test
It contains the single JUnit file named DummyControllerTest.java with code that should create a Component. I tried "testProvided", "testCompile" directives in build.gradle, both variants without success.
Thanks!
P.S. Christian, I cannot re-open my issue. Please do it by yourself if it's possible.

from dagger.

@cgruber why use android apt plugin ? Gradle and Android Studio are supposed to have annotation processor support out of the box, no ?

from dagger.

@stephanenicolas javac does annotation processing out of the box (unless told otherwise) by looking for processors in the classpath. So in that sense, yes, Gradle supports annotation processing out of the box. But Gradle is missing one thing: dependencies that you need when compiling but not at runtime (such as annotation processors; you don't want to package them into your application). Additionally, ideally, you'd want to be explicit about your processorpath, rather than just put annotation processors in the classpath: the processorpath is usually much smaller than the classpath so processor discovery is faster, but more importantly you know you're not bringing in an annotation processor that you didn't mean to use (for example, antlr' includes its own annotation processor: antlr/antlr4#487)

So you want an apt (or whatever its name) configuration that ends up filling javac's -processorpath, independently of the classpath. android-apt does just that, for Android builds.

from dagger.

And it also makes the generated sources visible to the IDE automatically.

from dagger.

OK guys, what's wrong with my example project? What I've missing? I can't use Dagger2 in tests, I didn't configured project well, something else? Any advice or hint please!

from dagger.