Releases should supply jar files where possible. Also, wherever Rx is used it should be optional and there should be a coroutine based alternative.
Actual behavior
Currently, every release supplies aar files. Libraries that are not required as "Android libraries" should be exposed as "Java libraries" (thusly generating jar files instead) so we can consume them in a wider variety of projects.
Steps to reproduce the behavior
Add any implementation call in gradle to any artifact from a pure kotlin project. The dependency fetched is an aar file which is not usable by a project that is not android related.
Progress:
[ ] utils-testing split into:
[ ] utils-testing-rx
[ ] utils-testing (if it makes sense to write the coroutine counterpart)
[ ] utils-testing-android
[ ] utils split into:
[ ] utils-rx
[ ] utils (if it makes sense to write the coroutine counterpart)
Expected behavior
Releases should supply
jarfiles where possible. Also, wherever Rx is used it should be optional and there should be a coroutine based alternative.Actual behavior
Currently, every release supplies
aarfiles. Libraries that are not required as "Android libraries" should be exposed as "Java libraries" (thusly generatingjarfiles instead) so we can consume them in a wider variety of projects.Steps to reproduce the behavior
Add any
implementationcall in gradle to any artifact from a pure kotlin project. The dependency fetched is anaarfile which is not usable by a project that is not android related.Progress:
[ ]
utils-testingsplit into:utils-testing-rxutils-testing(if it makes sense to write the coroutine counterpart)utils-testing-android[ ]
utilssplit into:utils-rxutils(if it makes sense to write the coroutine counterpart)utils-android