Eclipse 3.0 and previous was shipped such that each plug-in was a directory that contained code in a JAR, along with multiple other files. In order to improve the number of files that we ship along with the size of the Eclipse distributions, we have added support in Eclipse to be able to ship each plug-in as a single JAR file containing its code and other resources.
Converting A Plug-in to be Shipped as a JAR
manifest.mf
then simply delete the Bundle-Classpath
header.plugin.xml
then change the library
entry to be a dot like this: <runtime>
<library name=".">
<export name="*"/>
</library>
</runtime>
build.properties
:(.)
bin.includes
line. For instance,
if your bin.includes
line used to have core.jar
,
that will be replaced with a .
.For instance: bin.includes=about.html,.,META-INF/MANIFEST.MF
source.foo.jar=
to source..=
(that
is source dot dot)output.foo.jar=
to output..=
(that
is output dot dot)jars.compile.order
, etcmanifest.mf
, then add META-INF/
to the bin.includes
.<plugin>
tag: unpack="false"
about.html
linked content.about.html
with no linked files, then
you don't need to do anything.about.html
file, then that content must be placed in a directory named "about_files"
at the root of the plug-in.about.html
to point
to the new location of the files! If you have a custom build script (build.xml
):
If you have other scripts (e.g. javadoc generation scripts):