Skip to content

Commit 65b3247

Browse files
committed
Rework the readme slightly
1 parent 19305f9 commit 65b3247

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,9 @@ disable the JAR Cache (see above), unless reinitiated:
172172
RDF implementation specific code
173173
--------------------------------
174174

175-
All code specific to various RDF implementations (e.g. jena, sesame, etc) are stored in the [integration modules](./integration). Readmes for how to use these modules should be present in their respective folders.
175+
All code specific to various RDF implementations are stored in the [integration modules](./integration). Readmes for how to use these modules should be present in their respective folders.
176+
177+
The implementation specific integration classes for both Sesame and Jena have been moved into their respective codebases.
176178

177179
PLAYGROUND
178180
----------
@@ -187,14 +189,14 @@ This is a simple application which provides command line access to JSON-LD funct
187189

188190
run the following to get usage details:
189191

190-
./jsonldplayground
192+
./jsonldplayground --help
191193

192194
For Developers
193195
--------------
194196

195197
### Compiling & Packaging
196198

197-
`jsonld-java` uses maven to compile. From the base `jsonld-java` module run `mvn install -DskipTests=true` to install the jar into your local maven repository.
199+
`jsonld-java` uses maven to compile. From the base `jsonld-java` module run `mvn clean install` to install the jar into your local maven repository.
198200

199201

200202
### Running tests
@@ -239,7 +241,7 @@ CHANGELOG
239241
=========
240242

241243
### 2015-08-25
242-
* Deprecate Sesame-2.7 module in favour of sesame-rio-jsonld for Sesame-2.8 and 4.0
244+
* Remove Sesame-2.7 module in favour of sesame-rio-jsonld for Sesame-2.8 and 4.0
243245
* Fix bug where parsing did not fail if content was present after the end of a full JSON top level element
244246

245247
### 2015-03-12

0 commit comments

Comments
 (0)