Re: [cross-project-issues-dev] Deprecating the command line JAR signing

[Sam Davis <sam.davis@xxxxxxxxxxx>]

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?

Sam

--
Sam Davis
Senior Software Engineer, Tasktop
Committer, Eclipse Mylyn
http://tasktop.com

On Tue, May 29, 2018 at 2:49 PM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:

On Tue, May 29, 2018 at 11:40 PM, Andreas Sewe <andreas.sewe@xxxxxxxxxxxxxx> wrote:

Hi Sam,

> Actually, I am still not able to get this to work. It resolves the
> plugin now but it doesn't seem to do anything.
>
> The documentation for eclipse-jarsigner is a bit lacking. I would assume
> that if you invoke the plugin from a pom, it will replace all .jar files
> in the directory containing that pom, and its subdirectories, with
> signed versions, but that doesn't seem to be happening.
>
> How is it meant to work?

I had to resort to the Wayback Machine, but an old blog post I wrote
some years ago might help:
<https://web.archive.org/web/20170422050428/http://www.codetrails.com/blog/sign-your-eclipse-project>
Explains signing plugins, features, and all things pack200.

maybe you can contribute this to the Tycho project to improve their documentation ?

-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