Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Jubula: Invalid signature with eclipse-signing-maven-plugin

We recently made the switch over to the eclipse-signing-maven-plugin for repacking, signing, and packing the Jubula project, using as a reference (for job and pom). After the switch, I noticed that the produced p2 repository contained at least one invalidly signed jar (org.eclipse.jubula.client.core). The jar in question contains classes compiled from generated code, but other than that, I'm not sure what would cause this jar to be handled any differently from the others.

In the job, the following error occurs while performing the pack/repack operation after conditioning and signing:
Processing /opt/users/hudsonbuild/workspace/jubula-nightly/jubula/

[ERROR] STDERR: Exception in thread "main" java.lang.SecurityException: SHA1 digest error for org/eclipse/jubula/client/core/gen/parser/parameter/parser/Parser.class STDERR: at
STDERR:     at java.util.jar.JarVerifier.processEntry(
STDERR:     at java.util.jar.JarVerifier.update(
STDERR: at java.util.jar.JarVerifier$ STDERR: at STDERR: at STDERR: at
STDERR:     at
STDERR:     at
STDERR:     at
STDERR: at STDERR: at STDERR: at STDERR: at STDERR: at STDERR: at STDERR: at$DoPack.readClass( STDERR: at$ STDERR: at
STDERR:     at

The job succeeds despite that error, but running "jarsigner -verify org.eclipse.jubula.client.core_$VERSION.jar" on the resulting repo produces the same error. Has anybody encountered a similar error or could offer some advice?

 - Zeb

Mauernstr. 33
38100 Braunschweig

Tel.: +49-531-24330-0
Fax:  +49-531-24330-99

Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Back to the top