google/dagger not be found about dagger HOT 21 CLOSED

Yes - we have not released google/dagger as until the 2.0 product, which is
not quite ready for an initial release, our version and square/dagger were
largely identical with very minor internal differences.

We likely will not release com.google.dagger:dagger until we release 2.0
though I hope to start producing snapshots to try out next week.

On 3 September 2014 19:44, Daichi Furiya (Wasabeef) <
[email protected]> wrote:

http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.google.dagger%22%20a%3A%22dagger%22

https://bintray.com/bintray/jcenter/com.google.dagger%3dagger/view

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

from dagger.

thanks

from dagger.

any update? Will a SNAPSHOT be available before 2.0 release?

from dagger.

Any update ;-)? I simply can't wait!

from dagger.

Heh. Snapshot this week.

On Mon, Oct 6, 2014, 23:02 Radek Piekarz [email protected] wrote:

Any update ;-)? I simply can't wait!

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

from dagger.

Hm, I still can't find it in Maven Central - where do I go to download it?

from dagger.

@stephanos There aren't any snapshot in Central. Dagger is deployed to Sonatype OSSRH: https://oss.sonatype.org/content/repositories/snapshots/

from dagger.

@tbroyer Fantastic. Thanks!
Can you assess how mature it is already?

from dagger.

The Dagger 2 implementation should be stable, but the API is still subject to change (though likely in very straightforward ways).

from dagger.

@gk5885 That's great to hear! We want to replace Guice with Dagger as soon as possible.

from dagger.

Oh, but I should note that certain errors are not in place. Scope misuse and the like will not generate the appropriate errors. So, a bit of buy beware there.

from dagger.

We'll take it for a test spin soon and report back :)

from dagger.

Update in the next day or so BTW.

On Mon, Oct 27, 2014, 12:33 Stephan Behnke [email protected] wrote:

We'll take it for a test spin soon and report back :)

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

from dagger.

@cgruber @gk5885 If I see correctly google.dagger 2.0 still requires to specify the 'inject' property of the @module. Is there ANY way we wouldn't have to write all of those by hand (my related SO question)? We'd need hundreds ...

PS: Sorry for discussing this hear but my post to the dagger mailing list from 3+ days ago was not 'accepted' yet.

from dagger.

I think that there's a bit of confusion about Dagger 2. The only
property on @module that d2 pays any attention to is includes. From the
looks of your stack overflow question, you are still trying to use
ObjectGraph with dagger 2, but that is a strictly d1 API. D2 replaces the
ObjectGraph with @component and component interfaces.

On Wed Oct 29 2014 at 6:38:03 AM Stephan Behnke [email protected]
wrote:

@cgruber https://github.com/cgruber @gk5885 https://github.com/gk5885
If I see correctly google.dagger 2.0 still requires to specify the 'inject'
property of the @module https://github.com/Module. Is there ANY way we
wouldn't have to write all of those by hand (my related SO question
http://stackoverflow.com/questions/26610072/how-to-integrate-wicket-and-dagger)?
We'd need hundreds ...

PS: Sorry for discussing this hear but my post to the dagger mailing list
from 3+ days ago was not 'accepted' yet.

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

from dagger.

Oh. Is there any documentation, tutorial or example I can look at to get a grasp on Dagger 2?
(the examples in this repository don't seem to use @component)

from dagger.

They will after this PR is merged.

from dagger.

After looking at the examples I'm quite not sure how I would integrate Dagger with something like Wicket and Jersey. Both allow to inject components when a new page/resource is created. With Guice for example you simply call getInstance(object.getClass()). Dagger 2 does not have a central graph/injector anymore.

Do you have an idea how to integrate this dynamic nature of Jersey/Wicket with the static nature of Dagger 2?

from dagger.

@stephanos I was wondering too, but I'd say it's out of scope for Dagger. I was thinking one could use another annotation processor on the @Component annotation to produce a “service locator” (similar to Dagger 1's ObjectGraph) that dispatches to the appropriate method of the component.

from dagger.

*> but I'd say it's out of scope for Dagger. *

I hope not because as I see it that would really limit Daggers use with
server side frameworks like Jersey (and Dagger 1 wasn't limited that way).

So I too am hoping for a positive answer on this question.

Cheers, Rob.

On 31 October 2014 01:26, Thomas Broyer [email protected] wrote:

@stephanos https://github.com/stephanos I was wondering too, but I'd
say it's out of scope for Dagger. I was thinking one could use another
annotation processor on the @component annotation to produce a “service
locator” (similar to Dagger 1's ObjectGraph) that dispatches to the
appropriate method of the component.

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

from dagger.

@stephanos FYI, here's a proof of concept bringing the ObjectGraph API to Dagger 2: https://github.com/tbroyer/bullet

from dagger.