.releng

automation, application, assembly, and angst

Jar Signing Tips

As of M5, most of the projects I’m responsible for building now include jar signing & packing. The rest will soon follow. Here are a few lessons I’ve learned.

• Do not try to sign your jars between 00:00 and 01:00.
• The following are not the same:
  

   <include name="**/org.eclipse.draw2d*" />
  <include name=”**/org.eclipse.draw2d*/*” />
  <include name=”**/org.eclipse.draw2d*/**” />

• Forgetting the “-r” when zipping a file can lead to missing/corrupt sources and MANIFEST.MF files.
• If your build process never gets its signed zip back from build.eclipse.org, try not running the same build on two servers at the same time, as the filenames will collide.
• If you copied the Platform’s scripts for jar signing and find that you occasionally have build failures due to Permission denied or Host key authentication errors, try this fix.

Posted March 7th, 2008 by in category: ant, build, errata, scripting
You can skip to the end and leave a response. Pinging is currently not allowed.

Leave a Reply

You must be logged in using your Eclipse Bugzilla account to post a comment.