Eclipse Community Forums: Eclipse 4 » workbench.xmi not updated?

Home » Eclipse Projects » Eclipse 4 » workbench.xmi not updated?(My app is updated but the old xmi is loaded)

workbench.xmi not updated? [message #1268490]

Mon, 10 March 2014 11:12

Eclipse User

Hello,

I have an E4 app that updates itself at startup, based on an update site.

Today I corrected a bug related to key bindings, and pushed a new version. The app correctly updated itself at launch but the bug was still there.

I finally found out that by deleting the file located at ".metadata/plugins/org.eclipse.e4.workbench/workspace.xmi" and restarting, the bug disapeared.

What are the rules that trigger the creation of a new workspace.xmi file? Is it something that I can force at startup time?

Thanks for your help,

Sébastien

Re: workbench.xmi not updated? [message #1268878 is a reply to message #1268490]

Tue, 11 March 2014 01:00

Eclipse User

Use -clearPersistedState option.

[Updated on: Tue, 11 March 2014 01:00] by Moderator

Re: workbench.xmi not updated? [message #1268912 is a reply to message #1268878]

Tue, 11 March 2014 02:07

Eclipse User

Hi,

Thanks for your answer.

It's true that using the option to clear the persisted state solves the problem, but I'm not going to ask my users to do it. It's a technical operation they do not need to worry about.

The situation here is that I deploy a new version of the app but the old version's XMI is still used. What should I do to prevent that?

Re: workbench.xmi not updated? [message #1268944 is a reply to message #1268912]

Tue, 11 March 2014 03:05

Eclipse User

Open you product and you can add this option under Launching Argument. See the below image.
index.php/fa/17698/0/

Attachment: Untitled.png
(Size: 48.62KB, Downloaded 3172 times)

Re: workbench.xmi not updated? [message #1268969 is a reply to message #1268944]

Tue, 11 March 2014 03:59

Eclipse User

I think he generally wants persist the state and not clear it always, so
what he needs is a way to clear it only when the application is updated.

I don't think there's a general solution in place for e4 and one has to
develop ones own. A custom solution I could think of is to use the
lifecycle PostContextCreate and proactively remove the workbench.xmi
when an update is detected on the first start after the update.

I think that we (=e4) should provide a general solution to this problem
so I'd like you to file a bug and ask for a solution provide by the
framework!

Tom

On 11.03.14 08:05, sumit singh wrote:
> Open you product and you can add this option under Launching Argument. See the below image.
>

Re: workbench.xmi not updated? [message #1269045 is a reply to message #1268969]

Tue, 11 March 2014 06:05

Eclipse User

Thanks Thomas, I'll do that right away. Where should I open it? Platform/Runtime? Or E4/Runtime?

Re: workbench.xmi not updated? [message #1269058 is a reply to message #1269045]

Tue, 11 March 2014 06:20

Eclipse User

I think Platform/UI is the right component

Tom

On 11.03.14 11:05, Sebastien Pennec wrote:
> Thanks Thomas, I'll do that right away. Where should I open it?
> Platform/Runtime? Or E4/Runtime?

Re: workbench.xmi not updated? [message #1269098 is a reply to message #1269058]

Tue, 11 March 2014 07:25

Eclipse User

Here's the link to the bug entry: https://bugs.eclipse.org/bugs/show_bug.cgi?id=430090

Previous Topic:	set max item count for PartStack
Next Topic:	FolderLayout / PartStack stay open in compatibility mode

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 27 16:41:11 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter