Signing has been fixed on build.eclipse.org. I broke it last week when
I moved the staging area to faster local disks on the build server but
forgot to update the signing script.
Apologies for the breakage. Do I get a clown nose?
D.
Kim Moir wrote:
This is the problem.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=175367
The signing process at eclipse.org
is
now returning non-signed jars.
Kim
Hi,
I'm trying to sign jars and I'm following the procedure described here:
http://wiki.eclipse.org/index.php/JAR_Signing
The process works fine but Eclipse still complains the jars are not
signed.
Jarsigner also fails to verify the signed jars:
hleung@utils:/home/data/httpd/download-staging.priv/tptp/4.4.0/signed>
jarsigner -verify
features/org.eclipse.tptp.monitoring.runtime_4.4.0.v200702160100--aZEOQzPET2OpON.jar
jarsigner: unexpected exception
jarsigner exception text: zip file closed
Has anyone seen this behaviour?
Thanks,
Sorin
----------------------
Sorin Stoian
IBM Toronto Lab
(905)413-5477
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc. -- http://www.eclipse.org/
Office: 613.224.9461 x224
Cell: 819.210.6481
denis.roy@xxxxxxxxxxx
|