Yeah, I generally keep the shaded Guava project closed at all times in Eclipse (or even get rid of it from the workspace). My impression is that most other devs
who use Eclipse do something similar.
---
A. Soroka
dandh988 wrote on 5/23/17 11:49 AM:
It was eclipse IDE causing issues by opening referenced projects and then using
another version of guava in its own stack. Random thing is that if you click on
the import that eclipse cannot find it takes you to the class in the correct
project but the IDE fails to compile the class and maven fails...
Dick
-------- Original message --------From: Andy Seaborne <[email protected]> Date:
21/05/2017 23:35 (GMT+00:00) To: [email protected] Subject: Re: Jena 3.2.0-rc1
issue
Did you manage to sort this out?
This might be caused by building clean but using "-Pdev" (where the
shaded Guava has not been built).
Andy
On 15/05/17 16:20, Dick Murray wrote:
This is probably me but...
I've got a collection of import errors in my Jena 3.2.0-rc1 fork, the
common issue being the import prefix "org.apache.jena.ext"...
i.e. import org.apache.jena.ext.com.google.common.cache.Cache ; in jena-arq
FactoryRDFCaching
I've checked the github apache jena repository and it has these imports...
Am I missing something?
D
