So I have been hacking away today at Android-Maven.

It's far from perfect, and I sure still have a hell of a lot to learn about Maven2 (and Android), but it at least is a starting point - it can build, install in the emulator, and run an Android app.
Right now it basically lets you define the directory layout rather than having to stick to the Android default (and it defaults to the Maven standard), and then builds your R.java resources file, then compiles to Java bytecode, then builds the Dalvik DEX files, then builds an APK file, and finally launches the emulator and installs/runs the app (and of course all of that is configurable if you only want a portion of those steps, via your POM).
To be perfectly honest, Maven is annoying as hell on several fronts, and the Android Eclipse plugin is far more productive than using Android-Maven. That said though, Android-Maven does come in handy for automated builds (continuous integration) and for those that don't use Eclipse ;). Also, relying on the IDE to do magic stuff for you is just not a good habit to be in. F5 should *not* be your build process. To that end I started down this path because I wanted some automated/repeatable process for Android builds, and Maven was the logical choice (not because it's the best, but because it has some good points, and it's what I can throw into Hudson/Cruise/etc). If you don't use Maven, at least use the ant builds the Android creator scripts start you off with.
I will keep banging on this as I go and learn more about both Android and Maven - so hopefully it will get better.
Chatter
1 sec ago
3 hours 22 min ago
1 day 5 hours ago
2 days 25 min ago
2 days 9 hours ago
2 days 19 hours ago
2 days 21 hours ago
3 days 3 hours ago
3 days 19 hours ago
3 days 22 hours ago