Reputation: 6083
I have an aar Android library that is also dependent on a number of open-source libraries (RetroFit, Picasso, Android Support Lib, etc) and Google Play Services. It turns out a lot of developers still want the old .jar and Eclipse support.
What would be the best route to go about doing this? Can I package a .jar and provide its dependencies individually?
Upvotes: 1
Views: 73
Reputation: 1007484
What would be the best route to go about doing this?
Create your JAR, then document what dependencies you have, with suitable links, so those using your JAR can download the dependent JARs.
Optionally, offer the JAR via a Maven-style artifact repository (e.g., Maven Central) and provide the dependency details in the POM, for those Eclipse users who are using Maven.
Or, point out to the Eclipse users that official Eclipse support is evaporating in a few months and so it is not worth it for you to invest in distributing a JAR.
The worst solution, by a long shot, is for you to try bundling the dependencies inside your JAR.
Upvotes: 1