OBO-Edit: Making OBO-Edit Installers

From GO Wiki
Revision as of 12:30, 30 June 2014 by Gail (talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

These instructions are for OBO-Edit project administrators who need to make official OBO-Edit releases.

Tools you will need to download

The OBO-Edit installers are currently generated by a Java installer builder called install4j, which unfortunately is not free--we are investigating Open Source alternatives. You will also need to install JavaHelp.

Things to check in OBO-Edit source tree

Be sure you are up to date (do an svn update). Look in build.xml (in the main OBO-Edit directory) and make sure the location for "javahelp_indexer" points to your "jhindexer" executable in your installed JavaHelp application. Also check the install4j properties in build.xml and make sure those point to the right places.

Make sure org/oboedit/resources/VERSION is up to date and that it does NOT end with a newline--that will screw up the jar_manifest. Emacs always seems to put in a newline, even if you try to delete it. I've found the best approach is to change the version number by using this handy little perl command (change the numbers as appropriate): perl -pi -e "s/28/29/" src/org/oboedit/resources/VERSION

Also, be sure to put a brief description of changes since the last release in the CHANGES file in the main OBO-Edit directory.

Generating the release

You should now be able to say "ant installers" and the installers for each platform will be automatically generated in the releases subdirectory. (Note that the platform-independent release doesn't use install4j--it's just a tar file.)

In order to upload the installers to SourceForge, you will need to be a project admin. Go to http://sourceforge.net/project/showfiles.php?group_id=36855&package_id=148487, then click on the red "Admin" tag and select "File Releases".

Return to OBO-Edit main page