|
Re: plugin classpath util jars [message #144965 is a reply to message #144931] |
Thu, 16 October 2003 15:13 |
rich boakes Messages: 76 Registered: July 2009 |
Member |
|
|
Hi,
S.Witte wrote:
> What is the (correct) way to include utility jar files into the
> plugin. And, of course, ship them with the deployable jar for
> the update site.
Recently I've gone down the path of creating a separate plugin for each
utility jar that I need to ship (setting the plugin version number to
match the release number of the wrapped jar file). In this way I'm able
to set library dependencies based on the eclipse model, and not
re-package the same libraries for every different feature variant I want
to ship.
Aside: I've started to wonder about the merit of a central Eclipse
repository for jar's that have been wrapped, and the possibility of an
automated lookup in cases where a class is not found... then download on
demand.
> I tried to put them in the build.properties like this:
> source.<project>.jar = src/
> bin.includes = plugin.xml,\
> *.jar,\
> icons,\
> <project>.jar,\
> lib/*.jar
A cautionary tale - if you're using wildcards in your bin.includes, be
sure not to include the directory where your output jar file will end up
- if you do, subsequent builds will recursively include the old output
jar from the previous build, eventually making it huge.
i.e. lose the first "*.jar".
source.<project>.jar = src/
bin.includes = plugin.xml,\
icons,\
<project>.jar,\
lib/*.jar
As for your error: this is a long-shot, but since everything else seems
normal... your problem *may* be in your build.xml file - did you
generate it before or after you populated the build.properties file?
(you have to do it after)
To be sure, try unzipping your output jar file and seeing if all the
expected content is there.
HTH
rich
--
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03855 seconds