if you have an android library with mainfest and resources, it is best to
use AAR.
On Monday, July 22, 2013 1:19:36 PM UTC-4, Traun Leyden wrote:
>
>
> For the Couchbase Lite android library, I've moved everything over to be
> based on Android Studio + Gradle. Now, lots of users are asking for
> Eclipse support (big surprise).
>
> Pretty much all the dependencies are in the form of external maven
> artifacts (.aar's):
>
> repositories {
> mavenCentral()
> maven {
> url "
> http://maven.hq.couchbase.com/nexus/content/repositories/releases/";
> }
> }
>
> dependencies {
>
> compile 'com.android.support:support-v4:13.0.+'
>
> compile fileTree(dir: 'libs', include: 'td_collator_so.jar') // hack
> to add .so objects (bit.ly/17pUlJ1)
>
> compile 'com.couchbase.cblite:CBLite:0.7.2'
> compile 'com.couchbase.cblite:CBLiteEktorp:0.7.4'
> compile 'com.couchbase.cblite:CBLiteJavascript:0.7.2'
>
> }
>
>
> is it possible to "port" this into something that Eclipse can handle?
>
> Which tools would be required here? I'm guessing
> m2eclipse-android-integration<https://code.google.com/a/eclipselabs.org/p/m2eclipse-android-integration/>?
>
>
>
> Will it be able to handle .aar dependencies?
>
> Any gotchas to be aware of before trying this?
>
>
>
>
--
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.
