Dagger does not seem to work with groovy-eclipse-compiler about dagger HOT 10 CLOSED

Groovy does not have annotation processing and as such this will never work.
On Feb 13, 2015 4:43 PM, "kuza55" [email protected] wrote:

Hi,

I have a mixed Java/Groovy project that I was interested in using Groovy
in, for which I am using the groovy-eclipse-compiler via the maven compiler
plugin.

It seems that this is somehow incompatible; I extracted the simple example
from it's parent pom, got it to compile, then attempted to switch compilers
and the moment I did so maven stopped generating sources.

Are there any plans to support such use of Dagger 2? Or is there a better
way to utilise Dagger 2 in a mixed Java/Groovy project being built using
Maven.

• Alex

—
Reply to this email directly or view it on GitHub
#122.

from dagger.

Thanks for the info; is there a possibility that the Java bits of my application could get to benefit from Dagger?

I'm mostly using Groovy for the business logic bits that have to deal with some highly nested JSON input that is painful to deal with in Java, so not having them participate in Dagger isn't the biggest issue.

I guess I could split it into two separate modules with different compilers, but that would force me to stop writing tests in Groovy.

from dagger.

Yes. Splitting it should work fine. As long as the annotated parts which
use Dagger go through a compiler which knows how to run annotation
processors it will work.
On Feb 13, 2015 6:03 PM, "kuza55" [email protected] wrote:

Thanks for the info; is there a possibility that the Java bits of my
application could get to benefit from Dagger?

I'm mostly using Groovy for the business logic bits that have to deal with
some highly nested JSON input that is painful to deal with in Java, so not
having them participate in Dagger isn't the biggest issue.

I guess I could split it into two separate modules with different
compilers.

—
Reply to this email directly or view it on GitHub
#122 (comment).

from dagger.

@kuza55 just keep all Dagger's things: Modules and Components in Java + javac, and inject in Groovy/Java code

from dagger.

I'm trusting @JakeWharton on this and closing this since we can't support this due to a limitation in Groovy.

from dagger.

Based on https://docs.gradle.org/2.4-rc-1/release-notes#support-for-“annotation-processing”-of-groovy-code I think @JakeWharton is wrong.

from dagger.

I'm pretty sure my comment pre-dates 2.4.

On Mon, Nov 9, 2015, 4:32 PM Thomas Broyer [email protected] wrote:

Based on
https://docs.gradle.org/2.4-rc-1/release-notes#support-for-“annotation-processing”-of-groovy-code
I think @JakeWharton https://github.com/JakeWharton is wrong.

—
Reply to this email directly or view it on GitHub
#122 (comment).

from dagger.

Ha, that would explain it ;-)

from dagger.

Yep. By at least 6 to 8 weeks.

On Mon, Nov 9, 2015, 4:36 PM Jake Wharton [email protected] wrote:

I'm pretty sure my comment pre-dates 2.4.

On Mon, Nov 9, 2015, 4:32 PM Thomas Broyer [email protected]
wrote:

Based on
https://docs.gradle.org/2.4-rc-1/release-notes#support-for-“annotation-processing”-of-groovy-code
I think @JakeWharton https://github.com/JakeWharton is wrong.

—
Reply to this email directly or view it on GitHub
#122 (comment).

from dagger.

This is definitely not a high priority for us, but if you can report back on the status of this as of Groovy 2.4 feel free to reopen and we can reconsider the scope.

from dagger.