Here's how to: http://uima.apache.org/dev-eclipse-plugin-signing
you get to this page via left-hand nav bar on UIMA -> Eclipse Update Sites -> Information for developers -> for information about plugin signing :-) (sorry it's buried) -Marshall On 4/6/2020 4:14 PM, Peter Klügl wrote: > Hi, > > Am 06.04.2020 um 20:42 schrieb Marshall Schor: >> Well, I wrote something incorrect, I think, re: the "signing" of the eclipse >> update site jars. >> >> Our current process (when signing is to be done) is to not sign them when >> voting >> on a release candidate, but sign them once the vote passes. >> >> If and when this vote passes, the jars can be signed. > > I lost track of the how to and I think my account isn't valid anymore. > Let's see. > > > Best, > > > Peter > > >> Cheers. -Marshall >> >> >> On 4/5/2020 9:45 AM, Marshall Schor wrote: >>> signature on source-release: OK >>> IssuesFixed: OK >>> compare svn w/ source-release: OK. >>> build from sources: Done on Windows, OK >>> Eclipse artifacts are not signed causing a warning when installing into >>> eclipse >>> Install into Eclipse 4.15 - OK. Created a new project, looked at files. >>> Release_notes and readme look fine. >>> spot check maven artifacts: ok >>> >>> spot check licenses/ notice: ok >>> >>> I noticed that the eclipse artifacts are still not signed. >>> This should be a straight-forward process, that would give >>> "installers" more confidence that they're installing something >>> official and not corrupted. It seems in this stage of the >>> world (?!?) this would be a good thing to do... :-) >>> >>> [X] +1 OK to release >>> >>> -Marshall Schor >>>
