Community
Participate
Working Groups
Steps to reproduce: 1. Create a new OSGi Bundle/Plug-in project with Bundle Root that is different from the Project Root. For example, create a new Web Application Bundle (WAB) project: http://wiki.eclipse.org/Libra/Getting_Started#Create_new_Web_Application_Bundle. In this case the Bundle Root is the /WebContent folder. 2. Create an OSGI-INF folder under the Bundle Root folder. In the case of WAB example /WebContent/OSGI-INF. 3. Call the New Component Definition wizard and create a new component.xml under the OSGI-INF folder. The component.xml is correctly created, but the MANIFEST.MF is incorrectly modified. The Service-Component header points to the component.xml, but the path is relative the Project Root instead of to the Bundle Root. In the WAB example, it looks like: Service-Component: WebContent/OSGI-INF/component.xml while it should look like: Service-Component: OSGI-INF/component.xml
Fixed in master. See DSCreationOperation.java. The file path that is entered in the manifest is now made relative to the bundle root rather than the second segment of the filepath.
Thank you for the fix, Curtis! I tested it with Juno and it works perfectly. Is it possible to downport the fix for Indigo SR2? This bug affects and adopter's scenario that is currently being developed on top of the Indigo stream.
Verified in I20111021-1625 and by the original reporter.