Community
Participate
Working Groups
Using Eclipse 3.2 RC7 This bug is very closely related to bug 138260 in that it asks for PDE to ensure that files required by a bundle at runtime are included in build.properties. The goal here is to ensure that the bundle is built accurately and does not surprise the developer at runtime. The value for the Bundle-Localization manifest header describes a file, with an optional path, that points at the properties file containing localized string values. It would be handy if the PDE could ensure that the localized file, and optional directory structure, be included in the build.properties. Please remember that if the Bundle-Localization header is NOT present in the manifest the default localization value is "OSGI-INF/l10n/bundle". This is described in section 3.2.1.8 of the OSGi R4 Core specification. So, if Bundle-Localization is not present in the manifest AND OSGI-INF/l10n/bundle.properties exists then PDE should ensure that OSGI-INF/l10n/bundle.properties is included in build.properties. This is easy to overlook. Without this validation it will be possible to build a bundle that does not behave as expected.
One addition to this, if the project is a 3.0 project, we need to remember to treat it accordingly (ie. plugin.properties).
*** Bug 206548 has been marked as a duplicate of this bug. ***
Adding a context to assist bugday people.
Created attachment 83252 [details] mylyn/context/zip
Created attachment 84128 [details] org.eclipse.pde.core.patch Here's a first stab at this code before I lose it in my workspace. Needs more testing before we release it.
Feel free to take a look at this code when you have time Brian. I hacked this up on the airplane and it seems to work in the important cases.
Ok, went through the test pass. Committing to HEAD in Simon's honor.
Created attachment 84415 [details] mylyn/context/zip
Thank you, Chris. Add one to my frosty beverage tab. ;-)
verified on I20071211-0010