Re: [cross-project-issues-dev] Deprecating the command line JAR signing service (aka /usr/bin/sign) - read if you use Buckminster
|The jarsigner plugins does not do anything on update sites. It must be run on eclipse-bundle and eclipse-feature packaging types. It must run in a maven step after the jar of the plugin/feature is build, and it will send it to the signing service, and replace the existing jar with a signed version.|
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
I have seen that page. The relevant part seems to be "Signs project main and attached artifacts using the Eclipse
jarsigner webservice. Only artifacts with .jar
extension are signed, other artifacts are not signed but a warning
message is logged." What does "project main and attached artifacts" mean?
I have this in a pom, and the build creates an update site under that directory and then runs the jarsigner plugin, but I am not seeing that anything is signed.
cross-project-issues-dev mailing listcross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Description: Message signed with OpenPGP