You could publish aar to local maven repo. On Friday, January 3, 2014 5:12:58 AM UTC-5, Jose Luis Huertas Fernández wrote: > > Hi, > > I'm struggling with the best way to distribute our library (non open > source). When I read about the .aar packaging I thought that was the > solution, but I'm still finding some limitations: > > > - It seems if I distribute our library as an aar, the only way for > developers to use it is placing it on a Maven repository because local > aar's aren't taken into account. Any plan to support this? > - Our library depends on some other internal projects (jars) that are > picked up from a Maven repo. The problem is these projects are just > internal organization, and I would like them to be included within the aar > once we release it. Is there anyway to instruct the library build process > to include these jars (or classes) inside the library? > - If we distribute our library only in aar format I guess people still > using Eclipse build system won't be able to use it, right? > > Any idea about how to overcome these limitations? > > Thanks, > > Jose Luis. >
-- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
