-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathREADME.txt
52 lines (33 loc) · 1.44 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
For full documentation, see the Wiki:
* http://code.google.com/p/owltools
== OWLTools Build Instructions ==
The OWLTools use maven as a build tool.
These instructions assume that a valid maven installation is available.
The recommended maven version is 3.0.x, whereby x denotes the latest
release for this branch.
=== Building OWLTools ===
* Option 1: Command line
1) Change into to the folder of OWLTools-Parent
2a) Run command: mvn clean package
This will trigger a complete build of all OWLTools projects
and generate the required jars for execution.
Remark: As part of the build the tests are executed. Any
failed test will stop the build.
2b) Build without test execution (Not Recommended)
Run command: mvn clean package -Dmaven.test.skip.exec=true
* Option 2: Eclipse
Requires either:
* Eclipse 3.7 OR
* Eclipse 3.6 with installed maven plugin m2e
Use the provided Eclipse launch configurations to trigger the build.
The configuration are located in the OWLTools-Parent/eclipse-configs
folder.
=== Running OWLTools (Unix and MacOS) ===
Running OWLTools requires a successful build, as described in the
previous section.
* OWLTools Command-Line Tools:
The executables and the generated jar are both located in:
OWLTools-Parent/bin
* OORT:
The executables and the generated jar are both located in:
OWLTools-Oort/bin