Simple and it works just fine. Great job 👍
Could you just add a unit test for this : Add two cyclic singleton bean in functional-test-1-5 project and add this test in functional-test-1-5-test :

@Test
public void cyclic_singleton() {
    EmptyActivityWithoutLayout_ context = new EmptyActivityWithoutLayout_();
    SomeCyclicSingletonA_ singletonA = SomeCyclicSingletonA_.getInstance_(context);
    SomeCyclicSingletonB_ singletonB = SomeCyclicSingletonB_.getInstance_(context);
    assertThat(singletonA.singletonB).isSameAs(singletonB);
}

Of cource, just give me a day :)

Is it ok?

Perfect 👍

Hi.

I'm having this issue and I'm using android annotations 2.7.1 in a maven project.

Sorry for stupid question.. but how can I get the version that solve this bug? In which version is it solved?

Thank you very much.

As you can see on related issue #770 this fix will be solved in 3.0 which should be release soon.

But if I need it VERY soon :)

If I want to use a non-release verison, but the current milestone?

2013/12/17 Damien notifications@github.com

As you can see on related issue #770https://github.com/excilys/androidannotations/issues/770this fix will be solved in 3.0 which should be release soon.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/792#issuecomment-30748135
.

The best way is to just solve the cyclic dependency by removing automatic injection in one of your bean and manually inject resources from Application.onCreate

Ok, I will do in this way waiting for new release 3.

Thank you!

2013/12/17 Damien notifications@github.com

The best way is to just solve the cyclic dependency by removing automatic
injection in one of your bean and manually inject resources from
Application.onCreate

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/792#issuecomment-30748617
.