Hi Chris,
I am on Linux, with Apache Maven 3.5.2, java openjdk version "1.8.0_151".
It works for me.
What is more, I can't line the stacktrace line numbers up with the code.
Jena 3.0.1 lines up better on
JournalControl.recoverSegment(JournalControl.java:185)
because that is a call to "replay"
I ran the maven compiled version with
java -cp target/classes:target/tdb_generator_resources/\* jena_test
and then
java -cp /home/afs/jlib/apache-jena-3.6.0/lib/\* tdb.tdbquery
--loc=my_dataset 'SELECT (count(*) as ?t) where {?a ?b ?c . }'
"tdbquery --version" ==>
Jena: VERSION: 3.7.0-SNAPSHOT
Jena: BUILD_DATE: 2018-02-27T22:54:52+0000
ARQ: VERSION: 3.7.0-SNAPSHOT
ARQ: BUILD_DATE: 2018-02-27T22:54:52+0000
RIOT: VERSION: 3.7.0-SNAPSHOT
RIOT: BUILD_DATE: 2018-02-27T22:54:52+0000
TDB: VERSION: ${project.version}
TDB: BUILD_DATE: ${build.time.xsd}
(the TDB bit is old junk in 3.6.0 - ignore it)
On 01/03/18 18:05, Chris Wood wrote:
java -jar .\target\jena_test.jar
The shade plugin wasn't configured to run, nor was it set to call the
right main class.
When I change the configuration, I also ran:
java -jar target/jena_test.jar
In all cases I got:
-----
| t |
=====
| 1 |
-----
So it's still a mystery to me, I'm afraid.
Andy
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>3.1.0</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
</execution>
</executions>
<configuration>
<shadedArtifactAttached>false</shadedArtifactAttached>
<transformers>
<mainClass>jena_test</mainClass>
....