Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have plugin signed #54

Open
frankbenoit opened this issue Jan 20, 2017 · 4 comments
Open

Have plugin signed #54

frankbenoit opened this issue Jan 20, 2017 · 4 comments

Comments

@frankbenoit
Copy link

To avoid this warning from eclipse while installing.

@rherrmann
Copy link
Owner

rherrmann commented Jan 20, 2017

While I think I could technically sign all bundles during build, I don't know where to get an official certificate (for free) to sign with. AFAIK, self-signed certificates still cause a warning dialog - at least when used for the first time.

@rherrmann
Copy link
Owner

After spending several hours trying to build, sign, and deploy either with Codeship (the currently used build and deployment tool) or Travis CI without success, I am giving up for now.

A pull request that produces a (self-) signed build and deploys to gh-pages would be welcome. An earlier attempt to build (without signing) on Travis CI can be found here: 5380279

@frankbenoit
Copy link
Author

Too bad you have this difficulties.
Should be the interest of Eclipse.org to make this procedure as easy as possible.

@rherrmann
Copy link
Owner

Eclipse.org has a facility to sign jars (with an Eclipse.org certificate), but Extras for Eclipse is not an Eclipse.org project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants