[android-developers] Re: Reusable code organization with Android Studio

2015-01-24 Thread Nobu Games
On Saturday, January 24, 2015 at 1:29:10 PM UTC-8, Doug wrote: Also, learn the semantics of what having -SNAPSHOT in a maven version string means for referencing build artifacts from a repo. Thanks for the pointer. That looks like the feature I was looking for. -- You received this message

[android-developers] Re: Reusable code organization with Android Studio

2015-01-24 Thread Doug
You could use a local maven repo, then write yourself a convenience script that automatically builds and installs everything from wherever you like it to live. Also, learn the semantics of what having -SNAPSHOT in a maven version string means for referencing build artifacts from a repo. If

[android-developers] Re: Reusable code organization with Android Studio

2015-01-24 Thread Nobu Games
Thanks for your input! On Friday, January 23, 2015 at 7:39:51 PM UTC-8, Grunthos wrote: - I keep app projects in separate repositories and *I import my custom library modules* - *Importing a module creates a copy of the original * - This means *redundancy* and *code

[android-developers] Re: Reusable code organization with Android Studio

2015-01-23 Thread Grunthos
Interesting post, I find myself in a similar posiion re libraries and, more generally, in trying to find realistic best practice guides. On Saturday, January 24, 2015 at 5:07:58 AM UTC+11, Nobu Games wrote: - *I use only a single massive repository *that is basically an Android Studio