You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ During the build process, we extract the git version and branch information. The
28
28
29
29
2a) Run command: `mvn clean install`: 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.
30
30
31
-
2b) Build without test execution (Not Recommended): Run command: mvn clean install -Dmaven.test.skip.exec=true
31
+
2b) Build without test execution (Not Recommended): Run command: mvn clean install -DskipTests
32
32
33
33
#### Option 2: Eclipse
34
34
@@ -43,6 +43,7 @@ Use the provided Eclipse launch configurations to trigger the build. The configu
43
43
44
44
Running OWLTools requires a successful build, as described in the previous section.
45
45
46
-
+ OWLTools Command-Line Tools: The executables and the generated jar are both located in `OWLTools-Runner/bin`
46
+
+ OWLTools Command-Line Tools: The build produces a combined executable bash script and jar, to be found in `OWLTools-Runner/bin`
47
+
or in the `OWLTools-Runner/target` directory
47
48
48
49
+ OORT: The executables and the generated jar are both located in `OWLTools-Oort/bin`
0 commit comments