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
As a workaround, you can add
-Declipse.p2.unsignedPolicy=allowat the end of your eclipse.ini to disable the warning.
Closing because it is very low priority and too much hassle to get this working across multiple computers.
Log in to post comments