eclipse - Android studio external library projects -


i'm moving eclipse android studio , set in eclipse: have several android app projects, depending on several library projects (some shared) within 1 workspace. in android studio first started creating project per app, realized have have library projects modules within each project uses them. mean duplicating library projects , including them in each app, highly redundant , require maintaining multiple copies of libraries.

so switched having apps , libraries modules within same project. works building creates other problems such version control issues since each module lives in separate version control repository.

what cleanest way have setup? , real question is, can have separate projects in share same external library projects?

note

with release of android studio 0.5.0, answer obsolete, i'll leave below reference. more up-to-date instructions, see how share single library source across multiple projects


in android studio, it's difficult have shared library projects, because it's limitation modules in project must live under same root folder; seems found out when tried solve problem making 1 big project includes everything. we're working on trying lift limitation.

the best answer right make library modules separate projects , have them publish local maven repository, , have dependent projects pull them in repo. means can't work on app + library module sources context of single project, unfortunately. bigger disadvantage source attachments library modules doesn't work yet, if you're trying debug app, you'll have difficulty stepping code in libraries.

i know isn't great answer, @ stage of android studio's evolution, it's best can do. know yours common use case, , it's priority support it.


Comments

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

SQL: Divide the sum of values in one table with the count of rows in another -