Skip to main content

[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

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 <matthias.sohn@xxxxxxxxx> wrote:
On Tue, May 29, 2018 at 11:55 PM, Sam Davis <sam.davis@xxxxxxxxxxx> 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 ?


-Matthias

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top