Open yhpark opened 10 years ago
Yes this is a tricky one. I guess we would ideally want two separate builds on maven central, one with noa api 8+, one without noa api 14+. I'll think about a clean way to organize that with gradle flavors.
I just looked through android gradle document and found this:
Important: When enabling publishing of non default, the Maven publishing plugin will publish these additional variants as extra packages (with classifier). This means that this is not really compatible with publishing to a maven repository. You should either publish a single variant to a repository OR enable all config publishing for inter-project dependencies. http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Library-Publication
So I guess it is not possible right now :(
Nah don't worry it's definitely possible. Example: https://github.com/chrisbanes/ActionBar-PullToRefresh is pushing 3 different artifacts for the same library.
I really hate to bring this up myself but it's reality that the large portion of devices out there is running on Android 2.x. Would you consider replace animation related package imports to NineOldAndroid?