Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345048 - Virgo fails to install manifests containing packages starting with a number, while Equinox doesn't
Summary: Virgo fails to install manifests containing packages starting with a number, ...
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 3.0.0.M04   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 trivial (vote)
Target Milestone: 3.0.0.M06   Edit
Assignee: Borislav Kapukaranov CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-07 01:49 EDT by Borislav Kapukaranov CLA
Modified: 2011-06-14 04:37 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Borislav Kapukaranov CLA 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 CLA 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 CLA 2011-05-16 11:48:46 EDT
This bug has an assignee, so changing status to ASSIGNED.
Comment 3 Borislav Kapukaranov CLA 2011-06-14 04:36:49 EDT
Fixed. Will be out in 3.0.0.M06.