I think I understand now. It seems like this plugin can only be used to sign a jar built in the same reactor. We sign our jars as in a final step as part of building an update site, so it seems like this plugin isn't going to work. It looks like it will be easier to just update our scripts to use the web service.
Sam -- Sam Davis Senior Software Engineer, Tasktop Committer, Eclipse Mylyn http://tasktop.com On Wed, May 30, 2018 at 9:37 AM, Sam Davis <[email protected]> wrote: > But an update site is just a directory containing bundle and feature jars. > How does the plugin decide which jars to send to the signing service? > > > -- > Sam Davis > Senior Software Engineer, Tasktop > Committer, Eclipse Mylyn > http://tasktop.com > > On Tue, May 29, 2018 at 11:45 PM, Mikaël Barbero <mikael.barbero@eclipse- > foundation.org> wrote: > >> 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 >> 📧 [email protected] >> 🐦 @mikbarbero >> >> Le 30 mai 2018 à 01:53, Sam Davis <[email protected]> a écrit : >> >> 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. >> >> Sam >> >> >> -- >> Sam Davis >> Senior Software Engineer, Tasktop >> Committer, Eclipse Mylyn >> http://tasktop.com >> >> On Tue, May 29, 2018 at 3:32 PM, Matthias Sohn <[email protected]> >> wrote: >> >>> On Tue, May 29, 2018 at 11:55 PM, Sam Davis <[email protected]> >>> wrote: >>> >>>> Thanks very much for the replies, but I'm still missing something very >>>> basic: what does the sign goal of eclipse-jarsigner-plugin actually >>>> do? What are its inputs and outputs? >>>> >>> >>> maybe [1] helps ? >>> >>> [1] https://www.eclipse.org/cbi/sitedocs/eclipse-jarsigner-plugi >>> n/sign-mojo.html >>> >>> -Matthias >>> >>> _______________________________________________ >>> cross-project-issues-dev mailing list >>> [email protected] >>> To change your delivery options, retrieve your password, or unsubscribe >>> from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >>> >> >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> >> >> >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev >> > >
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
