[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Deprecating the command line JAR signing service (aka /usr/bin/sign) - read if you use Buckminster
|
Hi,
A quick update about the termination date of the command line Jar signing service (aka /usr/bin/sign).
With Oxygen.3a GA being available since yesterday, a grace period of 4 weeks is now starting before shutdown.
The termination date is set to May 9th.
Cheers, Mikael
--
Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 🐦 @mikbarbero
Hi,
Effective immediately, we are deprecating the usage the command line signing service (aka /usr/bin/sign).
Most certainly, this will only affect you if you use Buckminster as a build system (because Buckminster can only sign jars via /usr/bin/sign service). If you use Tycho, you're not concerned.
There are two strategies for Buckminster users:
2- Deactivate signing in Buckminster and do the repacking and the signing phase as a post build step. You will need to do some shell scripting (in your CI instance) to browse all the jars, pack200/unpack200 them (aka repack) and then sign them. To sign a jar, you can use the webservice that the CBI maven plugin uses in the background (see the Jar signing web service documentation for details - https://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service_.28Instant.29).
Cheers, Mikael
--
Mikaël Barbero - Eclipse Foundation IT Services - Release Engineering 📱 (+33) 642 028 039 🐦 @mikbarbero
|
Attachment:
signature.asc
Description: Message signed with OpenPGP