Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Guava dependencies

Hi all,

 

 

I’ve just removed all deprecated usages of Google Guava APIs, so Papyrus is now compatible with newer versions of Guava libraries.

 

Papyrus depends on a few Guava 11.x libraries, so I’ve also changed all dependencies to Guava 11+. Previously, it used to be “exactly 11.x” for a few plug-ins, and >= 10.x for the others.


I’ve also explicitly included Guava 11.0.2 in the Papyrus feature, so that the installer doesn’t try to fetch the highest version >= 11.x

 

I’ve tested a fresh Luna M4 installation with the Papyrus Nightly/Luna update site, with and without other components.

 

-          Installing only Papyrus: Guava 10.x and 11.x are available. Everything works fine

-          Installing Papyrus + Extra + XText: Same results

-          Installing Code Recommenders in addition: Guava 14 becomes available, and for some reason, everything crashes

o   Apparently, XText is at fault here, and because Papyrus Luna now depends a lot on XText (ModelExplorer + Diagrams), Papyrus crashes

 

I don’t really understand the “FrameworkEvent ERROR” logs.

 

422745: Linkage error, if guava 13 is available

https://bugs.eclipse.org/bugs/show_bug.cgi?id=422745

__________________________

Camille Letavernier

+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx

CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)

Papyrus : http://www.eclipse.org/papyrus

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Ed Willink
Envoyé : vendredi 13 décembre 2013 20:06
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Guava dependencies

 

Hi

I just installed Papyrus again and when I tried to run the OCLinEcore editor in a nested Eclipse it fails with a bad com.google.collect.iterables.Iterables.filter signature.

When I disable Guava 14 for the nested Eclipse, it works.

When I uninstall Papyrus, my primary Eclipse no longer has Guava 14 at all.

So it seems that one of Papyrus' dependencies is making Guava 14 available. and its not compatible. Since the corresponding source bundle is missing, it is not easy to check the suspicious signature.

NB Guava 14 comes from "Eclipse Code Recommenders" and is not in Orbit.

    Regards

        Ed Willink

On 14/11/2013 10:01, LETAVERNIER Camille wrote:

Hi all,

 

 

A few Papyrus components depend on the Guava API. In Guava 10.0.0, some API have been deprecated. In Guava >= 11.0.0, these methods don’t exist anymore.

 

Most plug-ins declare a dependency to Guava >= 10.0.0, which means they are supposed to work with Guava 11 and Guava 12. However, they usually rely on these deprecated methods available only in Guava 10.x

 

There are two solutions:

 

-          Do not use deprecated APIs of Guava 10.x

-          Use an explicit dependency to Guava [10.0.0, 11.0.0) (i.e. excluding Guava >= 11.0.0)

 

Until this is fixed, there will be undeterministic behaviors and bugs, depending on the Eclipse installation and which versions of Guava are available @runtime.

 

Note that XText also reexports its dependency to Guava, but as Guava is not a singleton library, this should not have any impact on other plug-ins.

 

 

Thanks,
Camille

__________________________

Camille Letavernier

+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx

CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)

Papyrus : http://www.eclipse.org/papyrus

 




_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev




No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4158 / Virus Database: 3629/6836 - Release Date: 11/14/13

 

Back to the top