For those who work on projects with multiple developers such as open source projects, you'd realise that the way I've currently set up Maven is not very good for multi-developer projects.
It's also not a good idea to have passwords or computer specific SDK locations in your pom.xml file because each developer will need to change the pom.xml in order to compile the code.
If you're fine with using script files to pass arguments to Maven then that's fine. Otherwise, you can set up the Maven global settings.xml file.
Contents
- Part 1 - Installing Maven for Eclipse
- Part 2 - Compiling and building your APK
- Part 3 - Converting an existing Android project to a Maven project
- Part 4 - Share a library project using a local Maven repository
- Part 5 - How to debug your Android app with Maven?
- Part 6 - Sign your Android app APK for release
- Part 7 - Global properties and settings for Maven
Machine specific Maven settings
It can be located in either:
- %M2_HOME%/conf/settings.xml
- %USERPROFILE%\.m2\settings.xml (aka ~/.m2/settings.xml)
Either way, the guts of it looks the same.
Open up your settings.xml file (you may need to create it for the user specific one).
I use this to store the location of my Android SDK home folder, Android SDK Maven repository and information such as keystore file and passwords.
The profile named "variables" sets up some properties for us which is automatically filled into your pom.xml file when needed.
The Android Maven repository is set up so you don't have to do it in every pom.xml file you work on.
And lastly, active profiles tells Maven to always use these the variables profile.
Once you're done, you'll need to reload the settings into Eclipse (if you don't want to restart).
- Preferences
- Maven
- User settings
- Click "Reindex" to update the settings
And that's it! We've finally reached the end of the Maven journey!
Time to go full pro at Maven now! I mean if an ostrich can ski that good, what's YOUR excuse?
