Community
Participate
Working Groups
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.
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
This bug has an assignee, so changing status to ASSIGNED.
Fixed. Will be out in 3.0.0.M06.