Repository navigation
API classes are copied in projects #626
Description
Activity
I don't think the problem is that classes are both in the API jar and generated. (only MediaType is in the two places).
But the problem is that if you have both the main project and a library project that use AndroidAnnotations, the classes are generated in both projects with the same package which causes the classes conflict.So these classes should not be generated and should be placed in the API jar.
The idea behind generating classes at compile time was to reduce the size of the APK.
The behavior for this is to keep classes in AA-API only if it should be exposed to the developer (likeMediaType). And the classes used by generated code (likeBackgroundExecutor) should be generated too.So, I see some points here :
- MediaType is duplicated and should only be present in AA-API.
- The shared preferences classes (
LongPrefField,LongPrefEditorField, etc...) should also be in AA-API because there are used by developer while working with preferences. - We should also put
BackgroundExecutorin AA-API because of some custom possible uses. - HasViews, OnViewChangedListener and OnViewChangedNotifier should be generated.
These points should fix the problem I had. But in case of two projects using AA (a library and an application) I'm not sure this could help.
Just though about something... I said "HasViews, OnViewChangedListener and OnViewChangedNotifier should be generated." but I think
@EActivityis one of the most used annotations on this project. So, we could just keep them in AA-API project- added a commit that references this issue
on Jul 12, 2013 Merged.
Some API classes are copied in the developer project. As they are also in the API jar, Eclipse have some trouble to compile the project because of classes conflict in classpath. Maven seems to handle that very well.
We have to cleanup all these. I'll take a closer look on all this later this week.