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

Bug 352275

Summary: Empty org.osgi.framework.system.packages.extra causes "Invalid manifest header Export-Package"
Product: [Eclipse Project] Equinox Reporter: Stephen Evanchik <evanchsa>
Component: FrameworkAssignee: Thomas Watson <tjwatson>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: tjwatson
Version: unspecified   
Target Milestone: Juno M1   
Hardware: PC   
OS: Linux   
Whiteboard:
Attachments:
Description Flags
Example Equinox log with "Invalid manifest header Export-Package" none

Description Stephen Evanchik CLA 2011-07-16 13:55:48 EDT 
Build Identifier: I20110613-1736

In working with Eclipse Indigo (Eclipse 3.7) I noticed a different behavior in processing the org.osgi.framework.system.packages.extra property.

In the previous versions (3.4, 3.5 and 3.6) when the property is empty it is ignored.

In 3.7 the property is processed which causes the Framework's Export-Package to look like this:

 "some.package, another.package, "

The trailing "," and perhaps the trailing space causes the following exception:

java.lang.RuntimeException: Exception while creating System Bundle: Invalid manifest header Export-Package: <export package list here>

If I remove the empty org.osgi.framework.system.packages.extra key from my config.ini the Framework starts and all is well.

Reproducible: Always

Steps to Reproduce:
1. Place org.osgi.framework.system.packages.extra= in config.ini
2. Run the Framework
3. See the exception, Framework fails to start
Comment 1 Stephen Evanchik CLA 2011-07-16 13:56:59 EDT 
Created attachment 199788 [details]
Example Equinox log with "Invalid manifest header Export-Package"