Antelope as a Stand-Alone Application

As Antelope requires Ant to do anything useful, an Ant build file is provided that starts Antelope. This makes it easy to start Antelope on any platform, and makes it easy to set the proper classpath independent of any other classpath that may exist in your environment. It is assumed that you have a working installation of Ant on your system. The Antelope start script is named "run.xml" and can be found in the top level directory of your Antelope distribution.

Start Antelope by running:


    cd AntelopeApp_3.2.18
    ant -f run.xml

The first time you run this you will be asked to enter the location of the 'lib' directory of your Ant installation.

You can also install Antelope by hand. Antelope is packaged as a single jar file, Antelope.jar. Several other jar files may be necessary:

All of these jar files are included automatically in the classpath if you start Antelope with the run.xml file.

The manifest file for Antelope.jar specifies ant.jar is to be found on the classpath, so all that should be necessary to start Antelope is:

java -jar Antelope.jar

If using the optional.jar and/or tools.jar:

java -cp optional.jar:tools.jar -jar Antelope.jar

Here is Antelope running as a stand-alone application:

Figure 5.2. Antelope as a stand-alone application

Antelope as a stand-alone application

Antelope as a stand-alone application provides a few features not found in the plugin version. In the plugin version, these features are provided by jEdit, so are not duplicated. The additional features are:

Printing is not available in this version, but is on the feature list for implementation.