New, experimental process
- hg clone ssh://$USER@hg.kenai.com/scales~mercurial
- cd scales~mercurial
- mvn test
- mvn clean
- mvn -B -P release -DdryRun=true -Dtag=mojarra-scales-$VERSION -DautoVersionSubmodules=true -DpreparationGoals=install release:prepare
- mvn release:clean
- mvn -B -P release -Dtag=mojarra-scales-$VERSION -DautoVersionSubmodules=true -DpreparationGoals=install release:prepare
- mvn -B -Dtag=mojarra-scales-$VERSION -DautoVersionSubmodules=true -DreleaseProfiles=release release:perform
Old steps
NOTE: Currently, Scales requires JDK 5 to build. This limitation should soon be removed.
Create a branch from trunk workspace
The branch is named: MOJARRA_SCALES_x_y
Checkout the branch workspace
cd to the branch workspace
Anyone doing a release will need a build.properties that defines the value keystore.pass in the source root, as well as keystore.ks, which can be obtained from any authorized Scales developer.
Update the version numbers in the POMs and source files
The Maven release plugin should probably be used for this process, but I've had nothing but pain with it. For now, we'll do this manually.
Update the version number in the following files:
Update the MultiFileUpload component
The MultiFileUpload component needs to know the exact name of the jars it will need to tell the applet to request. That being so, those names and versions are hard-coded in the component itself. Yes, this is extremely icky, but it's working for now. :) At some point, that information will be pulled from the build (patches welcome! :). For the time being, it must be maintained by hand. Until that change is made, edit the following file:
Edit the value for DEP_JARS, making sure that the version numbers are correct.
Build the workspace
Commit the changes to the branch.
Tag the branch
Deploy to the Maven Repository ===
Merge to trunk
TBD
