Sign content of Eclipse plugins
This would get rid of the unsigned content warning that Eclipse gives when you install Spoofax into an existing Eclipse with default options. You can of course disable the warning, but it would be more professional looking to have Spoofax be signed, and probably slightly more secure. You can self-sign your plugins according to this blog post.
Obviously this is low priority.
Submitted by Jeff Smits on 24 June 2015 at 23:23
Issue Log
On 24 June 2015 at 23:24 Gabriël Konat tagged minor
On 24 June 2015 at 23:24 Gabriël Konat commented:
As a workaround, you can add
-Declipse.p2.unsignedPolicy=allowat the end of your eclipse.ini to disable the warning.
On 2 November 2015 at 16:23 Gabriël Konat tagged eclipse
On 29 April 2016 at 16:31 Gabriël Konat commented:
Closing because it is very low priority and too much hassle to get this working across multiple computers.
On 29 April 2016 at 16:31 Gabriël Konat closed this issue.
Log in to post comments