Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Reorganize JARs #80
The idea is now:
An alternative approach to cater the Android world would be to deliver a jar with all features, but provide Proguard rules that strip unused "server-stuff" away. I will take a look into this.
Still, I would like to keep the API in a separate jar. Right now the API is also included in the
Thoughts from Android developers?
referenced this issue
Apr 3, 2018
Yes, separating the API does no other caching library. Its tedious and some effort, but I would consider it as good practice for every other library as well.
I see the following advantages:
The separate packages help me a lot during development for decision making and keeping things clean and focused. Is this something that needs to last or is this something that I may change any time?
Still it is some effort and not seen by much other libs. So what would be the Cons? Comments?
At the moment I started the reorganization and will release a alpha version with the new jars.
Reopening. Decided to stay with
Also I found that some users actually use explicitly