Skip to content

Commit

Permalink
Merge pull request #80 from phyloref/clarify-readme
Browse files Browse the repository at this point in the history
@Shalsh23 kindly walked through the instructions in the README and made some suggestions for clarifying some of the steps. Thanks so much, Shalki!
  • Loading branch information
gaurav committed Apr 21, 2021
2 parents c8750db + f0c758d commit df2980f
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ can be used to resolve [phyloreferences](http://phyloref.org):
- You can also use the `/version` endpoint to test whether the software is
working. It will report on the version of JPhyloRef, OWLAPI and reasoner
being used.
- Note that no content is served at `/`; you will need to use `/version` to
test that the server is running.
- `java -jar jphyloref.jar test input.owl`: Test all the phyloreferences in
`input.owl` by comparing their resolution with the expected resolution recorded
in the file.
Expand All @@ -31,6 +33,8 @@ Development of JPhyloRef takes place in [our GitHub repository]. This includes [

# Build and execution instructions

Once you have downloaded the source code to your computer, you can compile and test the code by running `mvn test`.

JPhyloRef can be built from source by running `mvn package` from the root directory of this repository. This will create a JAR file in the `target/` directory, which can be executed by running,
for example:

Expand Down

0 comments on commit df2980f

Please sign in to comment.