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 you are the only one working on your app and all of its libraries, then just do whatever you want that's most convenient for you and don't worry about development conventions. Just stick everything in one repo and take control of it yourself. IMO conventions are mostly for teams that need to agree how collaborate well together. Doug On Friday, January 23, 2015 at 10:07:58 AM UTC-8, Nobu Games wrote: > > I set up a *Maven repository for my library modules* and add the needed > modules as dependencies to my app project > > - Very elegant, but... > - Every single tiny change in my library code requires rebuilding > and deploying the module. > - I also fear that I need to increase the version code / build > number every single time so the local Maven cache gets updated? I have > no > experience with this. :-/ > > > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" 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/d/optout.
