[
https://issues.apache.org/jira/browse/JENA-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215887#comment-17215887
]
Andy Seaborne commented on JENA-1980:
-------------------------------------
Sounds interesting!
The B+Tree code was forked into jena-dboe-trans-data /
org.apache.jena.dboe.trans.bplustree - with changes to make it copy-on-write to
work within transactions (MVCC).
Is this building with maven from the command line?
I run into unpredictable problems if I have Eclipse and from the command line
run maven. Eclipse is scanning the files and the both Eclipse and maven and
working on the file at the same time. May be IntelliJ has a related effect.
{noformat}
[INFO] Could not create Interface report class
java.lang.IllegalArgumentException: No classes found in
[org.apache.jena.assembler, org.apache.jena.datatypes,
org.apache.jena.enhanced, org.apache.jena.graph, org.apache.jena.mem,
org.apache.jena.n3, org.apache.jena.ontology, org.apache.jena.rdf,
org.apache.jena.rdfxml, org.apache.jena.reasoner, org.apache.jena.shared,
org.apache.jena.util, org.apache.jena.vocabulary]
at org.xenei.junit.contract.tooling.InterfaceReport.<init>
(InterfaceReport.java:166)
{noformat}
The classes must be there to execute the test that come next.
Then we have:
{noformat}
______________________________________________________
______________________________________________________
BUILDING SPLITTER
______________________________________________________
______________________________________________________
[ERROR] Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 4.156 s
<<< FAILURE! - in org.apache.jena.tdb.assembler.TS_TDBAssembler
[ERROR] createDatasetDirect(org.apache.jena.tdb.assembler.TestTDBAssembler)
Time elapsed: 2.24 s <<< ERROR!
java.lang.NullPointerException
at
org.apache.jena.tdb.assembler.TestTDBAssembler.createTest(TestTDBAssembler.java:83)
at
org.apache.jena.tdb.assembler.TestTDBAssembler.createDatasetDirect(TestTDBAssembler.java:68)
{noformat}
but line 83 (in 3.16.0 and current development - same for yoru caode?) is
"ds.close()" and ds has already been used so is not a null.
Trying to decompose the issue:
Can you build it clean, in an area that IntelliJ is not using and without your
work applied?
> Error with CacheGuava when compiling source
> -------------------------------------------
>
> Key: JENA-1980
> URL: https://issues.apache.org/jira/browse/JENA-1980
> Project: Apache Jena
> Issue Type: Question
> Components: Base
> Affects Versions: Jena 3.16.0
> Environment: IntelliJ 2020.2 on Windows.
> Reporter: Martin Pekár
> Priority: Critical
> Labels: build
> Fix For: Jena 3.16.0
>
> Attachments: output.txt
>
>
> When running the tests, or compiling the source, an error is returned
> indicating that package org.apache.jena.ext.com.google.common.cache does not
> exists. Furthermore, the last 4 plugins in the pom.xml file are not found by
> Maven. These are the following:
>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <version>2.17</version>
>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-jxr-plugin</artifactId>
> <version>2.5</version>
>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-pmd-plugin</artifactId>
> <version>3.8</version>
>
> <groupId>com.github.spotbugs</groupId>
> <artifactId>spotbugs-maven-plugin</artifactId>
> <version>3.1.1</version>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
