The integration of Otto consist in copying @Produce and @Subscribe annotations in the generated class, so the behavior will be the same.
More generally, all runtime annotations should be copied in the generated class so that the other framework won't even know that we are using AA and it should work fine.

The issue appears when you are using two annotations processors.
But, if you can specify the order of processing, you can have both frameworks working together.
For example, if you use AA and johncarl81's parceler, and parceler is processing after AA, you can annotate a class with both @EBEan and @Parcel and it will work fine because parceler will process both the base and the generated class.

About the frameworks integrated by AA, they are :

Otto : copying annotations will enable us to remove the integration (ProduceHandler and SubscribeHandler.
RoboGuice : There are annotations on fields, not method. So, there is no overriding so no problem.
GreenDroid, SherlockActionBar, HoloEverywhere : No annotations
OrmLite : It's not a common case to have a POJO being annotated with @EBean. But, if someone does it, it will need annotations to be copied to the generated class.

I hope I didn't forgot any integrated frameworks.

Honor Nullable/Nonnull method signature annotations when generating code #782

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions