[babel-dev] plugin.properties vs NL Fragments

[Pascal Essiembre <essiembre.pascal@xxxxxxxxxxxx>]

Hello,

 

For the Babel Messages Editor, I am trying to put all translations in a fragment, including the plugin.properties files.  The plugin.xml (or MANIFEST.MF) editor recognizes the puglin.properties files put in the fragment project (it pulls the right values for e.g. %plugin.name) but when I test the plugin by launching it in a new workspace (Run As.. Eclipse Application), the plugin.properties are not being recognized.  For example, a localized preference page name will not be interpreted property as it should (%pref.whatever will show up as opposed to its localized value).

 

They only are recognized if I leave them in the host plugin project (as opposed to fragment) and I include “Bundle-Localization: plugin” in the MANIFEST.MF file.    Is there a way to have the plugin.properties files being recognized by the platform when in fragments?

 

Thanks,

 

Pascal E.