Consider adding google/dagger

[perezd]

Could be a worthwhile addition to this since it requires some annotation processor setup as well much like Auto.

[ronshapiro]

You're right that we should do this. I haven't figured out exactly how we should be interfacing with libraries that use bazel-common yet, so I'm hesitant to rush to something too quickly. But if you use bazel-common and then add a workspace dep on Dagger, everything should work

[perezd]

Oh I suspect it will work, I just want bazel-common to do it for me :)

…

On Sun, Nov 18, 2018 at 7:01 PM Ron Shapiro ***@***.***> wrote: You're right that we should do this. I haven't figured out exactly how we should be interfacing with libraries that use bazel-common yet, so I'm hesitant to rush to something too quickly. But if you use bazel-common and then add a workspace dep on Dagger, everything should work — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#38 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABQdkqjHVExIFsOz_0p61_fwvESDFwNks5uwh7rgaJpZM4YoJYB> .

[perezd]

I think its probably best to just depend on the jars from maven, seems like Bazel-based integration is broken pretty badly at the moment.

[ronshapiro]

I don't think that's a reason to rush this unfortunately. I don't think it's something we want long term.

But we can fix any of those issues (thanks for reporting them)! so that we can get things up to speed.