[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- From: Ben Konrath <bkonrath@xxxxxxxxxx>
- Date: Mon, 05 Jun 2006 13:42:39 -0400
- Delivered-to: firstname.lastname@example.org
Eclipse 3.2 includes a pre-made com.jcraft.jsch_0.1.28.jar plugin. This
plugin is basically jsch-0.1.28.jar repacked with OSGi metadata. Here's
some info as to why this was done:
There are two problems that this poses for linux distros: (1) we can no
longer symlink to the system jsch jar and (2) the eclipse build process
does not have procedure for building this plugin.
I can't think any way to avoid having two versions of the same class
files on the system. What I'm thinking about doing is re-creating the
plugin jar by doing the following during the build:
* unpacking the regular jar
* pulling the OSGi metadata from the pre-built plugin jar
* deleting this pre-made plugin jar
* re-packing the plugin jar with the class files from the regular jar
and the metadata from the plugin jar
So jsch would become just a build requirement and not a runtime
requirement. I think this is kinda lame, though, so if anybody has any
other suggestions that would be cool.
This may be a problem for the com.ibm.icu plugins as well. I haven't
looked into it yet, but there are in the same location as the
com.jcraft.jsch_0.1.28.jar plugin within the sourceIncluded zip.