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

Bug 360192

Summary:	pde target bundles can not work if they require system.bundle
Product:	[Eclipse Project] PDE	Reporter:	David Williams <david_williams>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.7.1
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description David Williams

2011-10-06 23:18:21 EDT

I was surprised this evening, trying to created a "special case" environment, that bundles such as xerces from orbit can not be be added to PDE target runtime. If selected, they result in an error message that says: 

Missing requirement: ... xerces ... requires 'bundle org.eclipse.osgi 0.0.0' but it could not be found. 

This would be, for example, be seen by adding the following repository to "the main" target (which consists of "running platform")

http://download.eclipse.org/tools/orbit/downloads/drops/R20110523182458/repository/

You can see similar messages (for other bundles) by just trying to select all bundles in the repo. 

This sure limits the usefulness of using target runtimes. Not sure if a bug or simply a limitation ... but ... is certainly limiting if its just not possible. 

Not sure if this is a "PDE issue", or "p2 issues" (or something else) but thought I'd open it here to start.

Comment 1 Curtis Windatt

2011-10-07 11:34:23 EDT

This is by design.  When you add the p2 location to your target, you have selected 'include required software'.  This will check that all the required pieces for the unit you have selected are available in the target and give you an error if this is not the case.

The two solutions for your problem are:

1) Turn off 'include required software'.  Turning this off will make the target download all required software that is available from the repo you have selected, but will not give an error if there is something missing.

2) Add the missing software. Add a second p2 location, point it at the Eclipse SDK or some other piece containing org.eclipse.osgi and everything should resolve correctly.