<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi All,<div><br></div><div>I thought that this will be an interesting discussion ;-)</div><div><br></div><div>My GSoC proposal mentioned movement to Maven because…</div><div>* It is really easy to manage dependencies.</div><div>* It is really easy to manage lifecycle: compiling, dexing, obfuscating, aligning.</div><div>* It is possible to check code style, catch some bugs and run tests as well.</div><div>* It is really easy to use anywhere: IDE, console — it does not really matter.</div><div><br></div><div>The current building is based on keeping libraries in the source tree which is not a perfect solution.</div><div>Maven downloads dependencies and plugins from Maven Central — a repository for artifacts (libraries).</div><div>It is possible to use other repositories and create new ones of course.</div><div><br></div><div>I meant using Maven as a tool, not compiling it when building an application (or I don’t understand something).</div><div>Maven is a build tool, like make, but with really heavy steroids.</div><div><br></div><div>You can look at my open source application as an example of Maven usage [1].</div><div>Maven files are pom.xml, application/pom.xml and tests/pom.xml.</div><div><br></div><div>The current version of the project uses Ant (yes, we already have a build tool inside a build tool so you can build while you build) which will be deprecated because there will be a new build system [2].</div><div>The new build system is based on Gradle. I decided not to use it now because it is kind of a beta.</div><div>Google announced Android Studio — IDE based on IntelliJ IDEA and it uses the new build system as well.</div><div><br></div><div>So my goal is to prepare a transition to the new build system. Migration from Maven to Gradle is really easy.</div><div>I repeat — Ant will be deprecated, Gradle is not ready enough, so I picked up Maven as the best solution at moment.</div><div><br></div><div>About Tinderbox. The only command for building an application with Maven is “mvn clean package”, so I see no troubles with that.</div><div><br></div><div>I am not against of moving mobile apps (Android and iOS) to separate repositories.</div><div>The only issue I see is a code review process — now it is possible to use Gerrit and I do not know is it possible to use it for multiple repositories.</div><div><br></div><div>Sorry for the large text — I just want to clarify things.</div><div><br></div><div>Regards,</div><div>Artur.</div><div><br></div><div>[1]: <a href="https://github.com/ming13/gambit">https://github.com/ming13/gambit</a></div><div>[2]: <a href="https://developers.google.com/events/io/sessions/325236644">https://developers.google.com/events/io/sessions/325236644</a></div></body></html>