| PDE Build: unpacked signed plugins get corrupted when jar-ing for updatesite [message #321534] |
Fri, 19 October 2007 05:55  |
Eclipse User |
|
|
|
Originally posted by: beat.strasser.inventage.com
Hi there
In our PDE build, we have to create our eclipse-based client *and* its
updatesite. There are plugins that have to be unpacked (especially
org.eclipse.equinox.launcher.(win32,gtk...)), but for the updatesite, we
need all of them packed in JAR files.
Our build currently jars everything for the update site (using the
property outputUpdateJars=true) and afterwards, it unpacks the features
and some plugins for a standalone client version.
The problem is that the build uses jar to build all the plugin/feature jar
files. But the JAR tool may change the MANIFEST file - and the plugin
signatures get corrupted. When I do the same thing directly with ZIP, the
signature is ok.
What's the preferred way to build an update site? We'd like to have valid
signatures, so our update mechanism and the about dialog work without
error.
Thanks for any hint,
Beat Strasser
|
|
|
| Re: PDE Build: unpacked signed plugins get corrupted when jar-ing for updatesite [message #321554 is a reply to message #321534] |
Fri, 19 October 2007 11:48  |
| Eclipse User |
|
|
|
We do have an open bug about this in pde.build, the problem does come from the
Jar tool changing the manifest. https://bugs.eclipse.org/bugs/show_bug.cgi?id=196754
You should build for the update site first, using outputUpdateJars (like you are
doing) These are the jars that you should sign.
You can then re-package these jars using the packager
http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse. pde.doc.user/guide/tasks/pde_packager.htm
I think there is also an example in our slides from Eclipsecon
http://aniefer.blogspot.com/2007/08/pde-build-slides-from-ec lipsecon-2007.html
The one trick is that before doing the packaging, you would need to unjar only
the plugins that need to be in folder-form. The Eclipse build itself does this
using an UnpackUpdateJars task it provides in
org.eclipse.releng.basebuilder/plugins/org.eclipse.build.too ls.
-Andrew
Beat Strasser wrote:
> Hi there
>
> In our PDE build, we have to create our eclipse-based client *and* its
> updatesite. There are plugins that have to be unpacked (especially
> org.eclipse.equinox.launcher.(win32,gtk...)), but for the updatesite, we
> need all of them packed in JAR files.
>
> Our build currently jars everything for the update site (using the
> property outputUpdateJars=true) and afterwards, it unpacks the features
> and some plugins for a standalone client version.
>
> The problem is that the build uses jar to build all the plugin/feature jar
> files. But the JAR tool may change the MANIFEST file - and the plugin
> signatures get corrupted. When I do the same thing directly with ZIP, the
> signature is ok.
>
> What's the preferred way to build an update site? We'd like to have valid
> signatures, so our update mechanism and the about dialog work without
> error.
>
> Thanks for any hint,
> Beat Strasser
|
|
|
Powered by
FUDForum. Page generated in 0.47194 seconds
Home