Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 299045

Summary:	Add option to independantly clean self hosting p2 data area
Product:	[Eclipse Project] PDE	Reporter:	Curtis Windatt <curtis.windatt.public>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	kane.mx, kane.zhu
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug
Bug Depends on:	291873
Bug Blocks:

Description Curtis Windatt

2010-01-07 10:15:28 EST

Extension of bug 291873.

The p2 data area created when self hosting is currently set to be inside the metadata folder.  If the configuration area of the launch config is cleared, the p2 data is also deleted.

From bug 291873:

The current fix is that putting the p2 data beneath the configuration when
launching the RCP in PDE. The p2 data would be cleaned if checking the option
to clean the configuration data when running/debugging the RCP. However, p2
data and OSGi configuration are totally different. You can see the official
release of Eclipse also put them in different folders,
configuration/,
p2/.

When I develop the our RCP, I want to clean the OSGi cache to let the changes
of MANIFEST take effect, and keep the p2 data. The profile data is useful for
our development, recovering it need cost some time to install some things. 
So it's necessary to distinguish the p2 data and OSGi configuration data while
running RCP in PDE. The better solution is adding an option to indicate whether
cleaning up the p2 data.

Comment 1 Curtis Windatt

2010-01-07 10:19:39 EST

I don't see us doing this for 3.6, as we have a lot of higher priority items.  However, I think we could make something like this work on the configuration tab.  We added a new area for "software installation" to turn on p2 profile generation.

However, 'p2' isn't used in the UI, so I"m not sure what we would call it.  In addition, not all targets get a p2 data area (only those launching with simple configurator).  So we would be adding complexity to the tab that wouldn't be used by everyone.

Comment 2 Lars Vogel

2019-11-27 07:26:28 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.