Repository navigation
Check the API Jar version #313
Description
Activity
We should also ensure that the annotation jar is in the classpath.
In case we find any of these problems, we skip the annotation processing alltogether.
Now the question is : how do we report these errors ? Compiler notes ? Compile error on a random element ?
What about this issue ? I think it's shouldn't be too complicated to detect if the API jar is not synchronized with the core. If we detect this problem we could stop the annotation processing and report this error on a random annotated element.
IMO this warning should be on all class level annotations, like
@EActivity,@EFragment,@EViewGroup,@EBean, etc...It's what I started to do in my current implementation :)
👍
Damn... I wanted to finish this one but it seems I lost my work... >_<
Merged
This is a follow up on #312.
We should introduce a way to identify each new version of the API Jar, and checks that the right API Jar is being used when processing the annotations. This would ensure both Jars are in sync.