Hi,
thanks for the reply.
In the mean-time I got a few steps further: I tried executing the mvn commands again (and likely in a different order). My Eclipse workspace looks quite OK right now.
The only problem I am currently seeing is that some of the "compliance" tests do not work when I execute them from within Eclipse. For instance when running "SHACLComplianceTest", I get the following exception:
java.lang.NoSuchMethodError: org.eclipse.rdf4j.sail.memory.MemoryStore.init()V
at org.eclipse.rdf4j.sail.shacl.ShaclSailConnection.getNewMemorySail(ShaclSailConnection.java:144)
at org.eclipse.rdf4j.sail.shacl.ShaclSailConnection.fillAddedAndRemovedStatementRepositories(ShaclSailConnection.java:326)
The classpath of the project within Eclipse looks OK though, and I don't see why it attempts to use a pre 2.5.x version of the Repository interface, where the init() method was not present. Is there maybe some "maven" magic in place for compliance tests that uses an older snapshot version somehow?
For reference: I used roughly the following steps for my setup
1) Clone repos, checkout latest master branch
2) rdf4j:
> mvn clean install -DskipTests
> mvn eclipse:clean eclipse:eclipse
=> import all project with prefix "rdf4j-" into the Eclipse workspace
3) rdf4j-storage:
> mvn clean install -DskipTests
> mvn eclipse:clean eclipse:eclipse
=> import all project with prefix "rdf4j-" into the Eclipse workspace
Can anybody confirm that this sequence is the appropriate way to setup the workspace? If not: what is the best way.
Regarding your question: I am currently using a JDK 1.8.0_192
Thanks,
Andreas