Creating an OJ release version
Jump to navigation
Jump to search
New Build/Release Procedure
The new build and release procedure uses maven.
Build and package procedure
Command line to build and package OpenJUMP with maven is
mvn package -P [release,]installer
- be aware that this will fail if no -P release is run beforehand, either at the same run or earlier
Release procedure
Command line to release a new version of OpenJUMP is
mvn package [-P <core,plus,[release> -D version.number=X.X.X [-D version.release=]]]
- you can select one or more profiles core, plus (both are the snapshots) or release (builds releases for CORE and PLUS)
- without a given profile CORE snapshot will be built by default
- for releases you might want to give a version.number (default=unknown) and a version.release (default=stable)
exemple
mvn package -P release -D version.number=1.5.1 -D version.release=stable
Old Release Process
- update the readme.txt
- summarize the changes to the previous version, based on the change log file (copy/sorting out)
- compile everything with the Ant script (check the java version to compile against)
- add the license, openjump.exe, and readme files (if not already included)
- so the platform independent zip & source release may be ready after copying the lic files into the zip (but best is to compare the zip content of an older release with the just created version)
- create a win-installer using Nullsoft NSIS (maybe with a pointer to download java 1.6) and include before-hand the ecw and mrsid libs into this edition (see also the notes on the svn for the past releases: e.g. for OJ 1.3.1)
- create another zip/release version that includes the sextante tools, postgis and print-plugin; based on the platform independent zip
- write the release notes
- upload the files to sourceforge
- make an announcement on slashgeo & our wiki & our sourceforge new section & change our webpage/links
- finally, updating of the documentation on the wiki on the new functions