-
Notifications
You must be signed in to change notification settings - Fork 33
Install OWLTools
This page documents two methods of installing owltools
There are two options to install the command-line version of OWLTools:
- Building from Source (the hard way)
- Downloading jars (the easy way)
See also: README.txt
Requirements:
- Git client
- Maven
The command line version should be obtained from the Github repository of this site. Clone the owltools git repository onto your machine. Change into the owltools directory and type the following:
cd owltools/OWLTools-Parent
mvn clean package
This will trigger a complete maven build of all OWLTools projects and generate the required jars for execution. For more details on maven see Maven How To.
A faster Maven build can be performed by skipping the Maven tests, and skipping the generation of Javadoc and source attachments. This type of build is useful after a successful initial installation to keep up with Git changes without doing a full build as described above. The command for this type of build is:
mvn -DskipTests=true -Dmaven.javadoc.skip=true -Dsource.skip=true clean package
You should now be able to run the wrapper script in the bin directory. For help:
./owltools/OWLTools-Runner/bin/owltools -h
You may want to add this to your $PATH
This option uses a pre-built JAR and script-wrapper instead of building owltools from the Java source. The JAR is built as part of the continuous building and test of the OWLTools project on a Jenkins server.
Go to http://build.berkeleybop.org/userContent/owltools/
Download:
- owltools (wrapper shell script)
- owltools-runner-all.jar (jar)
These should be placed in the same directory. E.g ~/bin/
If you add this to your PATH, you can run owltools on the command line:
owltools -h
Once you have the owltools script in your PATH, see wiki page for examples.