Repository navigation
Using annotations in abstract components #294
Description
Activity
Dublicate
Duplicate ? With which issue please ?
Hi @naixx
Thanks to you for helping AndroidAnnotations :)
I don't think that create an issue is a good way to get an answer. Could you use the mailing list to post your questions about AA ?
https://groups.google.com/forum/#!forum/androidannotations
Mathieu
No problems. It seemed to me a bug. I should post only a pull request or formulate this issue in another way.
Reopening :) #294 is an issue, #295 is a pull request to fix the issue, so there's no duplicate !
@matboniface Yeah this was a mix between a question and an issue. Since @naixx felt it was a bug, I think it's ok to post an issue :) .
In general, open discussions should go on the mailing list, and then move to bugs / features in issues, and then be fixed by a pull request. But that's only a general rule :)
We should also allow abstract classes for the other components :
@EApplication,@EBean,@EProvider,@EReceiver,@EService. I'm renaming this issue to match that need.
Why is it forbidden to use
@EFragmenton an abstract class? Just tried, everything seems OK.