|Re: Never ending exceptions in the version 0.10.0 [message #1096449 is a reply to message #1096441]
||Wed, 28 August 2013 12:06
| Ed Willink
Registered: July 2009
The old Guava problem was a migration of from collect to guava packages.
Hopefully that nightmare is well past.
The new nightmare is that Guava 12 started being used late in the Kepler
release cycle and Guava 12 mandates Java 6, whereas most Eclipse
projects support Java 5. So if you start up with a Java 5 JVM because
the crash may not occur for a long time (when a Java 6 function first
calls back). If you validate the plugins in your launch config it should
tell you, but we don't usually bother, partiucularly if it was one that
was ok when supplied by the developers, but is broken by the user's
The simple workaround is to make sure Java 5 is not available so that a
Java 6 JVM is used at the outset.
In Luna M1, MWE now mandates use of Java 6, so I suspect that the days
of Java 5 compatibility are numbered.
On 28/08/2013 12:56, Camille Letavernier wrote:
> I think there may be some version conflicts with the Guava library
> (com.google.*), depending on your installation.
> Papyrus should work with both 10.0.x and 11.0.x versions of Guava, and
> should also work fine if both versions are installed. However, in some
> cases, we've noticed such issues.
> I don't know how it can be solved. Reinstalling Eclipse/Papyrus should
Powered by FUDForum
. Page generated in 0.02296 seconds