[jira] [Commented] (SLING-6585) Switch to the ASF code signing service

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890449#comment-15890449 ] 

Robert Munteanu commented on SLING-6585:
----------------------------------------

I have started exploring converting the Ant task used by Apache Tomcat, which seemed to work well. For now I can't progress since there was a recent change which now requires me to use a client certificate and I have no idea where to upload it ( asked infra via email ).

Also, I have performed a test signing via the Web UI, which seemed to work, and replacing the artifacts in an existing update site did not seem to break anything. Anyway, to be sure, I have asked on the Eclipse p2 forums https://www.eclipse.org/forums/index.php/t/1084723/ . We may decide in the end to use the Web UI to sign the artifacts/features, if the Maven plug-in does not seem to be feasible.

> Switch to the ASF code signing service
> --------------------------------------
>
>                 Key: SLING-6585
>                 URL: https://issues.apache.org/jira/browse/SLING-6585
>             Project: Sling
>          Issue Type: Task
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>             Fix For: Sling Eclipse IDE 1.2.0
>
>
> The Eclipse tooling code signing was done with a personal certificate by myself. I am no longer able to use that, so if we want to keep signing the plug-ins, we should use the solution made available by the ASF ( see https://reference.apache.org/pmc/codesigning ).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)