Eclipse Community Forums: Papyrus » Never ending exceptions in the version 0.10.0

Home » Modeling » Papyrus » Never ending exceptions in the version 0.10.0

Never ending exceptions in the version 0.10.0 [message #1096438]

Wed, 28 August 2013 07:52

Eclipse User

Hi,

I have met with the similar problem in this topic: http://www.eclipse.org/forums/index.php?t=msg&th=487685/ while I am using the 0.10.0 version, there are mainly two kinds of exceptions:

The message is Problems occurred when invoking code from plug-in: "org.eclipse.e4.ui.workbench".

The first kind appears when I save the model:
java.lang.LinkageError: com/google/common/base/Optional
at org.eclipse.papyrus.uml.controlmode.profile.ControlledElementReadOnlyHandler.anyReadOnly(ControlledElementReadOnlyHandler.java:65)
at org.eclipse.papyrus.infra.emf.readonly.ReadOnlyManager.anyReadOnly(ReadOnlyManager.java:164)
at org.eclipse.papyrus.infra.core.resource.ModelSet.save(ModelSet.java:652)
at org.eclipse.papyrus.infra.core.lifecycleevents.SaveAndDirtyService.doSave(SaveAndDirtyService.java:275)
at org.eclipse.papyrus.infra.core.editor.CoreMultiDiagramEditor.doSave(CoreMultiDiagramEditor.java:798)
...

The second kind happened just after:
org.eclipse.e4.core.di.InjectionException: java.lang.LinkageError: com/google/common/base/Optional
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.setEnabled(HandlerServiceHandler.java:82)
at org.eclipse.core.commands.Command.setEnabled(Command.java:886)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.canExecute(HandlerServiceImpl.java:173)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.canExecuteItem(HandledContributionItem.java:864)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$2(HandledContributionItem.java:853)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$3.run(HandledContributionItem.java:231)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.updateItemEnablement(HandledContributionItem.java:261)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$ToolItemUpdateTimer.run(HandledContributionItem.java:152)
at org.eclipse.swt.widgets.Display.runTimer(Display.java:4271)
at org.eclipse.swt.widgets.Display.messageProc(Display.java:3358)

Those exceptions are just never ending, does anybody know why it is?

Thanks!

Re: Never ending exceptions in the version 0.10.0 [message #1096441 is a reply to message #1096438]

Wed, 28 August 2013 07:56

Eclipse User

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 #1096449 is a reply to message #1096441]

Wed, 28 August 2013 08:06

Eclipse User

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 #1096468 is a reply to message #1096449]

Wed, 28 August 2013 08:39

Eclipse User

Thank you for your very quick responses! I found the versions 10.0, 12.0 and 13.0 of Guava in the plugin repository, and after I removed the 12.0 and 13.0, there are no more problems, thanks again!

Re: Never ending exceptions in the version 0.10.0 [message #1096478 is a reply to message #1096468]

Wed, 28 August 2013 08:53

Eclipse User

Hello all,

I work with Jian on the topic, and I still have one additional question.
It appears that it is another dependency that forces the 13.0.0 version... (the Atlassian JIRA connector for Mylyn).
Hence, removing the dependency prevents us from using Mylyn with JIRA... Sad

Is there any possibility to let Papyrus use the last versions of Guava ? Is this something planned for a next version ?

Thx a lot in advance,

Maxence

Re: Never ending exceptions in the version 0.10.0 [message #1096481 is a reply to message #1096478]

Wed, 28 August 2013 08:58

Eclipse User

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 #1096508 is a reply to message #1096481]

Wed, 28 August 2013 09:31

Eclipse User

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 #1096509 is a reply to message #1096478]

Wed, 28 August 2013 09:31

Eclipse User

Hi

Have you tried just getting rid of your Java 5 JRE/JVM?

Regards

Ed Willink

On 28/08/2013 13:53, Maxence Vanbesien wrote:
> Hello all,
> I work with Jian on the topic, and I still have one additional question.
> It appears that it is another dependency that forces the 13.0.0
> version... (the Atlassian JIRA connector for Mylyn).
> Hence, removing the dependency prevents us from using Mylyn with
> JIRA... :(
>
> Is there any possibility to let Papyrus use the last versions of Guava
> ? Is this something planned for a next version ?
>
> Thx a lot in advance,
> Maxence

Re: Never ending exceptions in the version 0.10.0 [message #1096510 is a reply to message #1096481]

Wed, 28 August 2013 09:34

Eclipse User

Hi

For challenging products such as Guava it is best to minimize the
version bounds; impose just a knwon lower bound requirement, and hope
that whatever the user has is good.

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.

Regards

Ed Willink

On 28/08/2013 13:58, Camille Letavernier wrote:
> 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 10:24

Eclipse User

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.

Previous Topic:	Enable offline working on Papyrus Models
Next Topic:	Is there a SysML Model Library Repository?

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 16:45:51 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter