OBO-Edit: Making OBO-Edit Installers: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
These instructions are for OBO-Edit project administrators who need to make official OBO-Edit releases. | These instructions are for OBO-Edit project administrators who need to make official OBO-Edit releases. | ||
== Tools you will need to download == | |||
The [http://sourceforge.net/project/showfiles.php?group_id=36855&package_id=148487 OBO-Edit installers] are currently generated by a Java installer builder called [http://www.ej-technologies.com/products/install4j/overview.html install4j], which unfortunately is not free--we are investigating Open Source alternatives. You will also need to install [http://java.sun.com/products/javahelp/download_binary.html JavaHelp]. | The [http://sourceforge.net/project/showfiles.php?group_id=36855&package_id=148487 OBO-Edit installers] are currently generated by a Java installer builder called [http://www.ej-technologies.com/products/install4j/overview.html install4j], which unfortunately is not free--we are investigating Open Source alternatives. You will also need to install [http://java.sun.com/products/javahelp/download_binary.html JavaHelp]. | ||
Once you've | == Things to check in OBO-Edit source tree == | ||
Once you've downloaded install4j and JavaHelp, look at 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. Finally, make sure org/oboedit/resources/VERSION is up to date and put a brief description of changes since the last release in the CHANGES file in the main OBO-Edit directory. | |||
You should now be able to say "ant installers" and the installers for each platform will be automatically generated in the releases subdirectory. | == 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. Tada! You can | |||
[http://wiki.geneontology.org/index.php/OBO-Edit Return to OBO-Edit main page] | |||
Revision as of 14:02, 4 December 2007
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
Once you've downloaded install4j and JavaHelp, look at 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. Finally, make sure org/oboedit/resources/VERSION is up to date and 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. Tada! You can