Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342466 - Manifest parser allows packages to be seperated by comma and space
Summary: Manifest parser allows packages to be seperated by comma and space
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: Framework (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: equinox.framework-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-11 12:39 EDT by Frieder Heugel CLA
Modified: 2011-04-11 13:04 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frieder Heugel CLA 2011-04-11 12:39:44 EDT 
Build Identifier: 3.6.2

According to the OSGi core specification the only delimiter for packages in the Import/Export-Package header is , (comma). When deploying a bundle where packages are separated by comma and space Equinox doesn't complain. Moreover when packages are exported that begin with an arabic number Equinox again doesn't complain. Both scenarios fail when using Eclipse Virgo. See http://www.eclipse.org/forums/index.php?t=msg&th=207564&start=0 for more information.

Reproducible: Always
Comment 1 Thomas Watson CLA 2011-04-11 13:04:19 EDT 
In the R4.2 core specification: end of section 1.3.2 General Syntax Definitions:

<spec>
Whitespaces between terminals are ignored unless specifically noted. Any 
value that contains a space, a comma, semi-colon, colon, equal sign or any 
other character that is part of a terminal in the grammar must be quoted.
</spec>

As for checking that the package name is valid (i.e. does not start with an arabic number), we don't do any checking for this and I don't really think it is strictly required by the specification to fail installation because of it.