Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

testShacl.jar should be compiled on Travis #14

Open
gaurav opened this issue Nov 22, 2016 · 1 comment
Open

testShacl.jar should be compiled on Travis #14

gaurav opened this issue Nov 22, 2016 · 1 comment
Assignees
@gaurav
Labels
work on later

Comments

@gaurav
Copy link
Member

gaurav commented Nov 22, 2016

Right now, it needs to be compiled locally because of a strange error on Travis (https://travis-ci.org/gaurav/phylo2owl/builds/177837977#L923). When we have more time, I'd like to look into this and figure out why it isn't working.
@gaurav gaurav self-assigned this Nov 22, 2016
@gaurav gaurav mentioned this issue Nov 22, 2016
Merged
hlapp pushed a commit that referenced this issue Nov 22, 2016
@gaurav @hlapp
SHACL testing (#13)
5349dc7 
* Basic setup for testing SHACL.
* Basic SHACL test.
* Explicitly typed every Node as obo:CDAO_0000140.
* Command line options to check for version number and help.
* Python script that invokes Java program for testing.
* Install Java 8 and use Maven in Travis for CI testing
* For now, need to compile uber-JAR locally, then upload it for testing. See #14.
gaurav added a commit to gaurav/phylo2owl that referenced this issue Dec 29, 2016
@gaurav
Added the reasoner uber-JAR for testing instead of compiling it on Tr…
32e4d81 
…avis (see phyloref#14).
gaurav added a commit to gaurav/phylo2owl that referenced this issue Dec 29, 2016
@gaurav
Added the reasoner uber-JAR for testing instead of compiling it on Tr…
d9aa262 
…avis (see phyloref#14).
@gaurav
Copy link
Member Author

gaurav commented Jan 28, 2017

I managed to get the JAR file compiling successfully on Travis, and the ensuing JAR file is executable. However, when given a set of shapes to validate, it gives an error message:

Exception in thread "main" java.lang.NoSuchMethodError: org.apache.jena.sparql.core.assembler.AssemblerUtils.registerModel(Lorg/apache/jena/rdf/model/Resource;Lorg/apache/jena/assembler/Assembler;)V
at org.apache.jena.tdb.assembler.VocabTDB.init(VocabTDB.java:71)
at org.apache.jena.tdb.assembler.VocabTDB.(VocabTDB.java:64)
at org.apache.jena.tdb.assembler.AssemblerTDB.init(AssemblerTDB.java:25)
at org.apache.jena.tdb.TDB.init(TDB.java:251)
at org.apache.jena.tdb.sys.InitTDB.start(InitTDB.java:29)
at org.apache.jena.system.JenaSystem.lambda$init$1(JenaSystem.java:111)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:186)
at org.apache.jena.system.JenaSystem.forEach(JenaSystem.java:163)
at org.apache.jena.system.JenaSystem.init(JenaSystem.java:109)
at org.apache.jena.rdf.model.ModelFactory.(ModelFactory.java:49)
at org.topbraid.spin.util.JenaUtil.createDefaultModel(JenaUtil.java:311)
at org.topbraid.spin.util.JenaUtil.(JenaUtil.java:74)
at org.phyloref.phylo2owl.testShacl.main(testShacl.java:69)

I've figured out that the JAR files produced remotely and the one produced locally doesn't have exactly the same files in them, but they have all the files mentioned in the error message, so I'm still not sure what's causing this. Since we're fine producing JAR files locally for now, I'm going to hold off on this issue until it's needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaurav gaurav

Labels
work on later
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gaurav