| Note |
|---|
This guide assumes your module is maven-based, and stored in git. If you don't have a pom.xml file in your module, see Converting old code to Maven in before using this approach |
Background
While you are doing development in a maven module, your module's working version ends in -SNAPSHOT. By default, this will start at 1.0-SNAPSHOT.
...
The Maven Release Plugin automates nearly all of this.
Prerequisites
Credentials to the maven repository (you need to do this once in your dev environment)
You need to have a login to mavenrepo.openmrs.org. (This does not use your OpenMRS ID.) You can request an account at http://go.openmrs.org/helpdesk. Once you have a username and password to the maven repository, you can specify your username and password in settings.xml (in your ~/.m2 directory):
...
| Note |
|---|
If you don't want to type your username in clear text (note the password is saved in clear text to the file release.properties), you can try to set up maven password encryption. |
Settings in pom.xml (you need to do this once for any module you release)
The <scm> section of your module's root pom.xml needs to point to the urls that the module lives at. (Note that the maven module archetype incorrectly defaults these to point to svn, so you need to change these to point at github.) For example:
...
Don't forget to commit and push these configuration changes to github!
Doing the Release (the Maven part)
After configuring all the prerequisites, make sure you are pointing at the branch you want to release (normally "master") all your code is committed and pushed, and you have pulled the latest version from origin (and upstream, if relevant.)
...
When this completes, the particular git revision will have been tagged, and its compiled artifacts will have been deployed to our maven repository.
Uploading to the Module Repository (the manual part)
(Unfortunately this last step is manual. If you're interested in automating it, please volunteer on the dev mailing list!)
The steps you ran above with the mvn release plugin will have created your official module-x.y.omod file under omod/target, and deployed this to our maven repository so that developers can access it programmatically. For implementers to be able to access it manually, you need to upload it to the Module Repository. (You can log in using your OpenMRS ID.)