Repository navigation
Integrate with RoboGuice 2.0 #172
Description
Activity
I must be blind, created a duplicate.
Upgrade notes:
http://code.google.com/p/roboguice/wiki/UpgradingTo20The main difference that breaks compatibility with AndroidAnnotations seems to be that InjectorProvider has been removed, and instead RoboGuice.getInjector(Context) is used. It also no longer requires RoboApplication
Hi,
Have you worked on RoboGuice 2.0 support ?
Thanks.
No. It shouldn't require to much work, but I didn't have time to investigate that yet.
hi i would like this feature as well any ETA on this, seems like its been open for a while now
Yeah, sorry, but we have a lot on our plate and RoboGuice 2.0 support hasn't been a priority. I'd love to do it, just didn't have the time to do it yet.
On Thu, Oct 4, 2012 at 8:02 PM, Pierre-Yves Ricau
notifications@github.comwrote:Yeah, sorry, but we have a lot on our plate and RoboGuice 2.0 support
hasn't been a priority. I'd love to do it, just didn't have the time to do
it yet.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/172#issuecomment-9136446.No problem, i'm just started writing my 1st android app and your frramework
seems to be the most complete, but still missing a few things like form
validation. I'm sure the android frameworks and libraries etc will mature
more in the comings years more like the traditional java stuff.Hello! Are there any update on this issue?
As I see it's not included in roadmap yet.It's not in the roadmap because this hasn't been a priority for us. I haven't used RoboGuice 2.0. I'd rather consider integrating with Dagger than RoboGuice, but of course both aren't exclusive. If anyone is willing to give this a shot, please go ahead.
Hey,
Could you guys please take some time out and add the support for the RoboGuice 2.0 .
ThanksYep. I updated the milestone of this issue btw
RoboGuice 2.0 has just been release, we should provide the RoboActivity behavior without having to extend RoboActivity, as we did for RoboGuice 1. We should also do it for RoboFragment.
Should we support both versions, by looking in the build path for class that only exists in 2.0 ?