Eclipse Community Forums: Eclipse Platform » Standalone use of Eclipse tools creating workspace at runtime

Home » Eclipse Projects » Eclipse Platform » Standalone use of Eclipse tools creating workspace at runtime(When using EMF standalone (without the IDE, headless, or RCP), a workspace directory is created)

Show: Today's Messages :: Show Polls :: Message Navigator

Standalone use of Eclipse tools creating workspace at runtime [message #536042]

Wed, 26 May 2010 18:28

Jonathan Seng

Messages: 7
Registered: May 2010

Junior Member

I am using EMF in a standalone application -- that is, without the Eclipse IDE, RCP, or in a headless Eclipse execution. At runtime, a workspace directory is created containing a .metadata directory.

I am assuming this to be caused by the Eclipse Platform as opposed to EMF.

Can I prevent the creation of this directory or at least control where it is created?

Report message to a moderator

Re: Standalone use of Eclipse tools creating workspace at runtime [message #536184 is a reply to message #536042]

Thu, 27 May 2010 10:08

Prakash G.R.

Messages: 621
Registered: July 2009

Senior Member

On 26/05/10 11:58 PM, Jonathan Seng wrote:
> I am using EMF in a standalone application -- that is, without the
> Eclipse IDE, RCP, or in a headless Eclipse execution. At runtime, a
> workspace directory is created containing a .metadata directory.
>
> I am assuming this to be caused by the Eclipse Platform as opposed to EMF.
>
> Can I prevent the creation of this directory or at least control where
> it is created?

You can pass the -data option:
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/reference/misc/runtime-options.html

- Prakash
Platform UI Team, IBM

www.eclipse-tips.com

Report message to a moderator

Re: Standalone use of Eclipse tools creating workspace at runtime [message #537210 is a reply to message #536184]

Tue, 01 June 2010 15:26

Jonathan Seng

Messages: 7
Registered: May 2010

Junior Member

Thank you. I am now able to alter the location of the workspace directory.

The documentation also mentioned the VM option osgi.instance.area.readOnly; however, when set to true, the specified osgi.instance.area directory is still created.

Is this a defect or does readOnly mean 'after created'?

Thank you.

Report message to a moderator

Previous Topic:	view disposal: origin/cause
Next Topic:	[Common Navigator] Image Decorators with Custom Resource Backed Models

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 23:23:43 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter