|
|
| Re: Looking for a way to reference the product and plugin information from a common callback method [message #642644 is a reply to message #642543] |
Thu, 02 December 2010 02:19  |
Eclipse User |
|
|
|
Am 01.12.10 18:57, schrieb Paul Webster:
> drew wrote:
>> Typically we have placed the plugin product strings in the
>> plugin.properties file. The new project has a common mechanism that
>> stuffs this info in a separate callable class, is there a way for
>> plugin.xml to call out to a java method instead of read it from the
>> plugin.properties.
>
> No, OSGi uses Bundle-Localization to load a ResourceBundle. That's
> where it has to come from.
>
> Eclipse plugins can use the NLS classes, but not MANIFEST.MF or plugin.xml
>
> PW
>
>
I've been looking this translation system into this lately because of
the translation story in Eclipse 4.0 and the lookup of those
translations is handled by an OSGi-Service named BundleLocalization.
If the extension registry is a good citizen of OSGi and uses this
service you can at least in theory install a BundleLocalization-Service
ranked higher than the default one but this would mean that you need to
do what the orginal service does and only handle your special use case.
Tom
|
|
|
Powered by
FUDForum. Page generated in 0.24907 seconds
Home