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

Bug 402503

Summary:	Pre-launch validation should respect profile
Product:	[Eclipse Project] PDE	Reporter:	Jens Borrmann <jens.borrmann>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.8.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Jens Borrmann

2013-03-06 04:17:36 EST

We do not use equinox default runtime profiles (e.g. JavaSE-1.6.profile) but define our own profile. In this profile we add/change some of the values for org.osgi.framework.system.packages. We specify the usage of this profile in your OSGi launch configurations (-Dosgi.java.profile=ourCompany.profile). At runtime everything works like a charm.

But pre-launch validation results in errors caused by missing constraints. It seems that equinox default profiles are used during this validation step.

Just ignoring all reported issues that come from this problem is not feasible, since many bundles can be affected. Besides that real problems are obscured. In practice "validate bundles" becomes unusable, which is a pity - we value this feature very much.

Comment 1 Curtis Windatt

2013-03-06 10:35:11 EST

I would review a patch for this, but I do not have time to work on this myself at the moment.

Comment 2 Eclipse Genie

2019-09-30 17:08:09 EDT

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.

--
The automated Eclipse Genie.

Comment 3 Jens Borrmann

2019-10-07 01:19:33 EDT

We do not need this feature any longer. So as far as I am concerned this could be closed.