diff options
author | Thomas Wolf <twolf@apache.org> | 2023-09-11 20:58:15 +0200 |
---|---|---|
committer | Thomas Wolf <twolf@apache.org> | 2023-09-12 20:27:59 +0200 |
commit | e3798df6e810ab08d821f158e83fe0fd3fd0eb18 (patch) | |
tree | c9e4f6fd4fc5aaede9754bd394a157b3784489f9 /org.eclipse.jgit.ssh.jsch.test/tst/org/eclipse | |
parent | 82c6638c72cd9525bab94b02438c167747132be9 (diff) | |
download | jgit-e3798df6e810ab08d821f158e83fe0fd3fd0eb18.tar.gz jgit-e3798df6e810ab08d821f158e83fe0fd3fd0eb18.zip |
OSGi: move plugin localization to subdirectory
OSGi can have its plugin localization at an arbitrary place; there is
no need to have it in a top-level plugin.properties file. In non-OSGi
environments having the files at the root level may mean that these
files clash with each other, or, as in the referenced bug, with some
third-party plug-in's plugin.properties, which may not even have
anything to do with localization.
Move our OSGi localization to a subfolder OSGI-INF/l10n. For OSGi
environments, that's just as good, and for non-OSGi environments it
avoid clashes with other root level items on the classpath or in a fat
JAR.
For fragments, use neither plugin.properties (which would clash with the
host plug-in's plugin.properties) nor fragment.properties (which might
clash with other fragments for the same fragment host bundle). Instead
use names "relative" to the host bundle.
Bug: 582394
Change-Id: Ifbcd046d912e2cfe86c0f7259c5ca8de599d9aa1
Signed-off-by: Thomas Wolf <twolf@apache.org>
Diffstat (limited to 'org.eclipse.jgit.ssh.jsch.test/tst/org/eclipse')
0 files changed, 0 insertions, 0 deletions