Re: [orbit-dev] Fwd: [Hudson] Build failed in Hudson: orbit-recipes #35

[Matthias Sohn <matthias.sohn@xxxxxxxxx>]

the original Bouncycastle library is signed with a JCE signature.

So it looks like I have to strip the signature and resign it with a new JCE

signature which is required for JCE providers. Otherwise the JVM will refuse

to register bouncycastle as a JCE provider.

I am waiting for

https://bugs.eclipse.org/bugs/show_bug.cgi?id=467064 requesting JCE signing certificate to be ordered from Oracle

https://bugs.eclipse.org/bugs/show_bug.cgi?id=478088 requesting JCE signing to be supported by signing service

to be fixed so that I can use that to sign Bouncycastle in orbit-recipes.

We could strip the existing JCE signature and do standard eclipse-jarsigning until these bugs are fixed

and we can switch to JCE sign bouncycastle. Here's a patch trying to implement that:

https://git.eclipse.org/r/#/c/67506

Alternatively we could try to skip eclipse-jarsigner for bouncycastle in orbit-recipes, though I suspect

the existing JCE signatures would break since we have to exclude some classes/resources from these

jars due to legal reasons.

How could I skip eclipse-jarsigner for these artifacts ?

-Matthias

On Sun, Feb 28, 2016 at 2:17 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:

Hi,

Anyone know what this error means? Is the Bouncycastle already signed?

>
> [INFO] Bouncy Castle OpenPGP API .......................... FAILURE [  4.734 s]
> [INFO] Bouncy Castle PKIX, CMS, EAC, TSP, PKCS, OCSP, CMP, and CRMF APIs SKIPPED
> [INFO] Bouncy Castle Provider ............................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 05:22 min
> [INFO] Finished at: 2016-02-27T19:38:24-05:00
> [INFO] Final Memory: 59M/3509M
> [INFO] ------------------------------------------------------------------------
> [INFO] o.h.m.e.h.MavenExecutionResultHandler - Build failed with exception(s)
> [INFO] o.h.m.e.h.MavenExecutionResultHandler - [1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho.extras:tycho-pack200a-plugin:0.22.0:normalize (pack200-normalize) on project org.bouncycastle.bcpg-jdk15on: Could not pack200 normalize jar file /jobs/genie.orbit/orbit-recipes/workspace/bouncycastle/org.bouncycastle.bcpg-jdk15on_1.52.0/target/org.bouncycastle.bcpg-jdk15on-1.52.0-SNAPSHOT.jar
> [DEBUG] Closing connection to remote
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-pack200a-plugin:0.22.0:normalize (pack200-normalize) on project org.bouncycastle.bcpg-jdk15on: Could not pack200 normalize jar file /jobs/genie.orbit/orbit-recipes/workspace/bouncycastle/org.bouncycastle.bcpg-jdk15on_1.52.0/target/org.bouncycastle.bcpg-jdk15on-1.52.0-SNAPSHOT.jar: pack200:normalize cannot be called for signed jar /jobs/genie.orbit/orbit-recipes/workspace/bouncycastle/org.bouncycastle.bcpg-jdk15on_1.52.0/target/org.bouncycastle.bcpg-jdk15on-1.52.0-SNAPSHOT.jar -> [Help 1]



--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/


_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev