Project setup for creating third party libraries for Android

Posted by Jarle Hansen on Stack Overflow See other posts from Stack Overflow or by Jarle Hansen
Published on 2010-04-30T20:55:41Z Indexed on 2010/05/01 9:57 UTC
Read the original article Hit count: 408

Filed under:
|

Hi all,

I am creating a library for Android that others can include in their own project. So far I have been working on it as a normal Java project with JDK 1.6 setup as system library. This works just fine in Eclipse when I add the android.jar.

The issue comes when I try to my build script. I am running Gradle and doing a normal compile and test build cycle. My thoughts were that it does not matter if I compile it with a normal JDK, since this is not a standalone application. The benefits by creating a normal Java project is that Gradle does support this much better. My project also does not contain any UI at all. However, the problem is that of course android.jar and the JDK contains lots of the same classes and I think that this is what messes up my build script. Everything crashes when running the tests (the tests are in the same project under src/test/java).

My question is, how should I create this project that is meant to be included in Android projects as a third party library? Should I create it as an Android project in Eclipse even though I am only creating a library that does not use any of the UI features? Also, should the tests be in a separate project?

Thanks for all responses!

© Stack Overflow or respective owner

Related posts about android

Related posts about java