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

Bug 345048

Summary:	Virgo fails to install manifests containing packages starting with a number, while Equinox doesn't
Product:	[RT] Virgo	Reporter:	Borislav Kapukaranov <b.kapukaranov>
Component:	runtime	Assignee:	Borislav Kapukaranov <b.kapukaranov>
Status:	CLOSED FIXED	QA Contact:
Severity:	trivial
Priority:	P3	CC:	aschrijver, frieder.heugel, glyn.normington
Version:	3.0.0.M04
Target Milestone:	3.0.0.M06
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Borislav Kapukaranov

2011-05-07 01:49:28 EDT

When installing bundles that contain in their MANIFESTs number-starting packages Virgo fails to complete the operation.
The outcome of such installs is not defined by the OSGi specification and is left for the implementor to decide. That is why Equinox isn't performing any checks.

Maybe its better to align with them on this behavior and allow the install to complete but still produce a warning that the installed bundle's MANIFEST is *not* OSGi compliant.

Attached is a vaadin bundle that contains such number starting package names.

Comment 1 Borislav Kapukaranov

2011-05-07 01:52:56 EDT

The bundle is too big to be attached so here is a download link:
http://vaadin.com/downloading?package=release/6.5/6.5.4/vaadin-6.5.4.jar

Comment 2 Glyn Normington

2011-05-16 11:48:46 EDT

This bug has an assignee, so changing status to ASSIGNED.

Comment 3 Borislav Kapukaranov

2011-06-14 04:36:49 EDT

Fixed. Will be out in 3.0.0.M06.