|
|
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 Messages: 7670 Registered: July 2009 |
Senior Member |
|
|
Hi
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
additional plugins.
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.
Regards
Ed Willink
On 28/08/2013 12:56, Camille Letavernier wrote:
> Hi,
>
>
> 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
> work.
>
>
> Regards,
> Camille
|
|
|
|
|
|
Re: Never ending exceptions in the version 0.10.0 [message #1096508 is a reply to message #1096481] |
Wed, 28 August 2013 13:31 |
|
Hi, Camille,
I don't know that we need to restrict the version of Guava with an
upper bound. Papyrus should work fine with Guava 13 as long as the
user runs it in a Java 7 VM.
The only incompatibility issue here is between the JRE version and the
installed Guava version; it isn't really a Papyrus problem but a larger
integration/deployment problem.
cW
On 2013-08-28 12:58:12 +0000, Camille Letavernier said:
> Hi,
>
>
> Papyrus will move to Java 1.6 in Luna. Latest versions of Guava target
> Java 1.7 I believe, so no, we won't be moving to the latest version
> (We'll stick to 0.11)
>
> However, different versions of Guava are not supposed to create
> conflicts. I guess we haven't properly restricted the Guava version(s)
> to use in Papyrus. This is most likely something we can fix.
>
>
> Regards,
> Camille
|
|
|
|
|
Re: Never ending exceptions in the version 0.10.0 [message #1096535 is a reply to message #1096510] |
Wed, 28 August 2013 14:24 |
Camille Letavernier Messages: 952 Registered: February 2011 |
Senior Member |
|
|
Quote:If for instance Papyrus requires 10.x.x and Xtext requires 12.x.x and
JIRA requires 13.x.x then nothing can possibly work, whereas if everyone
is >=9.0.0 the user stands a chance.
Guava is (AFAIK) not a singleton plug-in, so it should work, I guess. I hope so, because some deprecated APIs in 0.10.0 have been removed in 0.11.0. So, if you're using them, you really need a [0.10.0, 0.11.0[ constraint.
Camille Letavernier
|
|
|
Powered by
FUDForum. Page generated in 0.24834 seconds