Rob,
I've not had problems recently but some time ago I got similar. In
fact, I get it for other dependencies as well and it seems ot be come
down to variation between Eclipse and the maven local repo. Once, they
got quite out of step and I deleted and did "mvn dependency:resolve" (I
tend to use the command line).
My current practice is not to have jena-base as an open project in Eclipse.
Andy
On 04/06/15 14:30, aj...@virginia.edu wrote:
I have had this problem since I began tinkering. The only solution I have found
is make sure that the jena-shaded-guava project is never open when any project
that refers to types therein is open. This isn't much of a burden, and I
suppose it has something to do with the Maven magic that is going on inside
jena-shaded-guava.
I'm not totally clear as to why Jena shades Guava into its own namespace-- is
it to avoid OSGi-exporting Guava packages? (We have something like that going
on in another project on which I work.)
---
A. Soroka
The University of Virginia Library
On Jun 4, 2015, at 9:22 AM, Rob Vesse <rve...@dotnetrdf.org> wrote:
Folks
Recently I've been having a lot of trouble getting Jena to build in Eclipse
which seems to be due to the use of the Shade plugin to Shade Guava. Any
module that has a reference to the shaded classes ends refuses to build with
various variations of the following error:
java.lang.NoClassDefFoundError:
org/apache/jena/ext/com/google/common/cache/RemovalNotification
Anybody else been having this issue? If so how did you resolve it?
Sometimes cleaning my workspace and/or doing a mvn package at the command
line seems to help but other times it doesn't
Rob
