Community
Participate
Working Groups
Due to legacy reasons I assume the default localization of bundles/plug-ins defaults to /plugin.properties. OSGi however specifies it to default to /OSGI-INF/l10n/bundle.properties. PDE ignores this fact. If the Bundle-Header does not contain a localization it will not correctly resolve the texts from the OSGi default localization. Furthermore when you want to externalize new strings it should localize them into the specified localization (which could be the default one if not specified) and not into /plugin.properties. I think changing this behaviour would not break existing plugins and new OSGi bundle localization would be much easier to do.
ok I have it almost finished. The only remaining problem are the non-refreshing tooltips that ManifestTextHover is producing. When I change the l10n file the model ManifestTextHover is not updated. The bundle editor seems to use 2 models. One I can update upon resource delta change, in WorkspacePluginModelManager.handleBundleManifestDelta() I call ((AbstractNLModel) model).resetNLResourceHelper(); But I need also to update the model that is used in ManifestTextHover. Anyone has a clue?
Created attachment 106597 [details] Patch changes default bundle localization to the default OSGi bundle localization
Created attachment 106598 [details] Additional patch for PDE core
Consider for 3.5
Created attachment 119099 [details] org.eclipse.pde.core.patch Updated patch to not break old-style plug-ins.
Created attachment 119100 [details] mylyn/context/zip
Created attachment 119156 [details] org.eclipse.pde.patch An updated patch to include a test case.
done. > 20091201 Thanks for your initial patch Philipp.
Created attachment 119172 [details] mylyn/context/zip
Chris, that test contains a typing error for the Bundle-SymbolicName :)
Thanks. Thankfully that's what wasn't being tested in this case, hah ;)