Caused by: java.lang.NullPointerException
at sun.security.pkcs.SignerInfo.getTimestamp (SignerInfo.java:568)
at sun.security.util.SignatureFileVerifier.getSigners (SignatureFileVerifier.java:724)
at sun.security.util.SignatureFileVerifier.processImpl (SignatureFileVerifier.java:295)
at sun.security.util.SignatureFileVerifier.process (SignatureFileVerifier.java:263)
at java.util.jar.JarVerifier.processEntry (JarVerifier.java:318)
at java.util.jar.JarVerifier.update (JarVerifier.java:230)
at java.util.jar.JarFile.initializeVerifier (JarFile.java:383)
at java.util.jar.JarFile.getInputStream (JarFile.java:455)
at com.sun.java.util.jar.pack.PackerImpl$DoPack$InFile.getInputStream (PackerImpl.java:392)
at com.sun.java.util.jar.pack.PackerImpl$DoPack.run (PackerImpl.java:480)
at com.sun.java.util.jar.pack.PackerImpl.pack (PackerImpl.java:100)
at org.eclipse.tycho.extras.pack200.Pack200Wrapper.pack (Pack200Wrapper.java:51)
at org.eclipse.tycho.extras.pack200.Pack200Wrapper.pack (Pack200Wrapper.java:41)
at org.eclipse.tycho.extras.pack200.Pack200Archiver.pack (Pack200Archiver.java:147)
at org.eclipse.tycho.extras.pack200.mojo.Pack200PackMojo.execute (Pack200PackMojo.java:79)
over multiply machines (windows and our build server)
I know it is not directly a tycho problem but does anybody know what that could be?
is that related to the timestamping server that we use?
It happens now and then
Weird thing is i would expect that the signing part that really uses a tsa i think would be a problem
But that seems be working fine?
--