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

Bug 337137

Summary: Launch validation does not consider version numbers for system packages
Product: [Eclipse Project] PDE Reporter: Jens Borrmann <jens.borrmann>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Jens Borrmann CLA 2011-02-14 10:37:55 EST 
Build Identifier:  20100917-0705

Launch configuration validation in general seems to consider system packages specified via VM arguments. By default these packages are exported with version 0.0.0. The OSGi-spec describes that also a version number can be added:

-Dorg.osgi.framework.system.packages=javax.xml.namespace;version="1.0.0"

This information is evaluated correctly at runtime, but not when validating the launch configuration before starting the framework. In our case we have a third party library importing javax.xml.namespace with a specified version number of 1.0.0.

Reproducible: Always

Steps to Reproduce:
1.create a bundle importing javax.xml.namespace;version="1.0.0"
2.create a new empty launch configuration just containg the OSGi runtime and the test bundle. Specify as an additional vm argument:
-Dorg.osgi.framework.system.packages=javax.xml.namespace;version="1.0.0"
3.Press the validate button or start with "validate bundle automatically prior to launching" checked.
Comment 1 Eclipse Genie CLA 2019-09-09 14:14:15 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 2 Jens Borrmann CLA 2019-09-10 01:35:05 EDT 
We no longer have pain with this issue. So as far as I am concerned this could be resolved as won't fix.