This website requires JavaScript.
Explore
Help
Sign In
motiejus
/
jgit
Watch
1
Fork
You've already forked jgit
0
Code
Releases
Activity
e3798df6e8
jgit
/
org.eclipse.jgit.junit
/
build.properties
6 lines
103 B
Properties
Raw
Normal View
History
Unescape
Escape
Partial revert "Switch build to Apache Felix maven-bundle-plugin" This restores the ability to build using just Eclipse without strange procedures, extra plugins and it is again possible to work on both JGit and EGit in the same Eclipse workspace with ease. Change-Id: I0af08127d507fbce186f428f1cdeff280f0ddcda Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com>
2010-01-10 14:46:33 +02:00
source..
=
src/
output..
=
bin/
bin.includes
=
META-INF/,\
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>
2023-09-11 21:58:15 +03:00
O
S
G
I
-
I
N
F
/
,
\
.