-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor com.riiablo.excel to use annotation processors #135
Comments
Thinking about this issue a bit more, I think it may not be as difficult as I previously thought. I may be able to stub out the dependent classes in the project if I cannot specify them as strings. E.g., create a |
Implemented as |
Disable :table:annotation-processor dependency Exclude com.riiablo.table.*.** from compile to improve performance
Caching is not enabled causing the annotation processor task to run on every build. I've decided to disable it in |
Fix for bf609ac not excluding during test sources compilation
This seems like the most appropriate way to handle generating the excel table serializers, however I've had a lot of trouble trying to decouple the
com.riiablo.excel
hierarchy to support this. The excel table code generation depends on the excel classes, while the serializer generation depends oncom.riiablo.io
.project(':core')
cannot act as it's own annotation processor because that creates a circular dependency (can't process itself if it needs itself to annotate process itself).Long story short, I'm abandoning this complication for the time being and moving to an automated dependency-driven gradle task. I think implementing this feature will require thought and refactoring to the core classes
com.riiablo.excel.Excel
,com.riiablo.excel.TxtParser
, andcom.riiablo.excel.Serializer
.http://hannesdorfmann.com/annotation-processing/annotationprocessing101
The text was updated successfully, but these errors were encountered: