java - Use external Bundle-Localization path in MANIFEST file -


MANIFEST.MF file has an entry to define, which * .properties files are loaded on runtime. These entries define names and related properties files that are used to translate the plugin string starting with the prefix "%" such as "% plugin.name"

  bundle - Localization: Plugin  

has a line in comparison to the plugin

 % plugin.name = Runtime plugin  

Attribute file can also be a name application. Properties, I have to define bundle-localization: app

, when the property files are inside the plugin directory all the "properties" I define Bundle-localization: property / application


My question: Can I define bundle -Localization path, which is outside the plug-in, like

  bundle-localization: ../properties/application  

It seems that Mani Hast localization object properties asks zipfile for searching the path to the file path and Jippth does not support this functionality.

How can I solve this problem?

No, you can not define the path that is outside the plug-in pieces except the bundle Is also considered.

In general, the bundles are not connected to any place on the disk, so that you can not really define what kind of way ../properties should be resolved. For example, install a bundle by using BundleContext #installBundle (string location, InputStream input) . The location parameter is the identity of the bundle and there is no meaning mark in it. The content of the bundle is read from the input stream. What will be the way out of the bundle?


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -