Adrián Rivero

I made a migration recently and it is working properly (using gradle 2.2.2)... so probably the issue is not a gradle problem..

On this issue, @dodgex sees the same benefits mentioned on #2200 , though simply "processing @EConfiguration classes first and keep the info about the available/provided beans" would mean to have...

@WonderCsabo , so for having this functionality on AA, then you're recommendation is instead go with Dagger? Maybe we should build a plugin for AA and Dagger, which in fact...

For multiple handles, we could simply make a light version. It could work "aggregating" info. Let's see, right now to make this in AA we simply "force" the user to...

Well, I guess that what I'm proposing could be applied to the Activity scope as well, probably another annotation would be better for this. But well, with fragments is quite...

On this case is the `@EBean` which should take care of the other annotation.. But well, there are several cases like this already on the code.. For instance, the `@EActivity`...

@dodgex the injection is really "handled" on the `@EBean`.. The new `BeanHolder` mechanism is implemented like this, for instance, for the Activity scope: ```java public static ActivityScopedBean_ getInstance_(Context context) {...

So, `@Bean` continues calling the normal `getInstance_` method like before

Well, this would be a validation, which can be done on the `@Bean`.. That would not change the current code I think. I think the validations are quite valid to...

@dodgex , this multi-annotation you are suggesting is definitely a generalization of my suggestion, since it will permit to make a simple annotation (`@ViewEvent`), and `@Click` or any other are...