HI Frank, On a quick look it appears that the problem is related to pack200 support. It looks like the JAR is being signed, then packed, and then repacked. Not really sure as there are two different paths involved (target/conditioner/plugins vs target/site/plugins). There is an order of operations between signing and packing that is important or else you get corrupted signatures, which seems to be what has happened here.
However the good news is that pack200 is deprecated and new releases should not use them anymore, so you (hopefully) just strip out the pack200 calls and then everything will work? I think just removing the pack parts of https://git.eclipse.org/r/plugins/gitiles/mylyn/org.eclipse.mylyn/+/refs/heads/master/org.eclipse.mylyn-site/pack-and-sign/build.xml will do the trick. HTH, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Sat, 27 Nov 2021 at 12:20, Frank Becker (Eclipse) < ecli...@frank-becker.de> wrote: > Hi, > > I want to build a new release for mylyn (based on the 3.25.x branch), > but after a series of solved problems I need some help. > > The problem is that I don't know how to solve the SHA-256 digest error ( > https://ci.eclipse.org/mylyn/view/Releases/job/mylyn-3.25.x-release/47/consoleFull) > in the pack goal. > > Thanks for your help > > Regards > Frank > _______________________________________________ > mylyn-dev mailing list > mylyn-...@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/mylyn-dev >
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
