|Re: 3.4 pde build not signing features [message #603351 is a reply to message #603311]
||Mon, 16 November 2009 16:35
| Andrew Niefer
Registered: July 2009
Yes, I think it is only signing jars. To get everything signed, you can |
set outputUpdateJars=true, which turns everything into a jar.
This is because things that are packaged as folders are never jarred at
any point, an build is basically using the jarsigner from the sdk which
I don't think does folders.
There is a bug, https://bugs.eclipse.org/bugs/show_bug.cgi?id=184316,
but there isn't really anything on it.
A 3.5 style "p2.gathering=true" build gets an implicit
outputUpdateJars=true since it is publishing to a repo.
Francis Upton wrote:
> I am running the headless build on 3.4.2 and trying to sign all of my
> features and plugin jar files. I added the following to my
> signJars = true
> sign.alias = codesigncert
> sign.keystore = /d/machine/cert/codesign/codesignstore
> sign.storepass = ***
> sign.keypass = ***
> It signed most of my plugin jars, but did not sign the features or the
> plugins that were marked as unpacked in the features.
> My features appear as directories in the final kit, not jar files.
> I can export a feature project (using 3.5) and it signs all of jars just
> fine, as well as package the features as jar files.
> 1) Will it only sign features/plugins that are actually in jar files?
> 2) If so, how to I get features to be in jar files?
Powered by FUDForum
. Page generated in 0.02084 seconds