From 4a34c35e41fe2d074e642195aa7daee4a8ab13f7 Mon Sep 17 00:00:00 2001 From: Eric Douglass Date: Thu, 4 May 2017 13:36:40 -0700 Subject: [PATCH] Updating readme for combined jar/script --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f7815473e..b40df43b6 100644 --- a/README.md +++ b/README.md @@ -28,7 +28,7 @@ During the build process, we extract the git version and branch information. The 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. -2b) Build without test execution (Not Recommended): Run command: mvn clean install -Dmaven.test.skip.exec=true +2b) Build without test execution (Not Recommended): Run command: mvn clean install -DskipTests #### Option 2: Eclipse @@ -43,6 +43,7 @@ Use the provided Eclipse launch configurations to trigger the build. The configu 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-Runner/bin` ++ OWLTools Command-Line Tools: The build produces a combined executable bash script and jar, to be found in `OWLTools-Runner/bin` +or in the `OWLTools-Runner/target` directory + OORT: The executables and the generated jar are both located in `OWLTools-Oort/bin`