[jira] [Resolved] (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:all-tabpanel ]

Robert Munteanu resolved SLING-6585.
------------------------------------
    Resolution: Fixed

With the latest changes to the {{codesign-maven-plugin}} I consider this solved. I will document the exact steps needed when I perform the next release of the IDE tooling.

I'm not releasing the plugin yet, hopefully I can find another place for it other than Sling. However, that does not block us from using the plugin for signing the release from the git tag, by applying the patch locally.

> 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
>            Priority: Major
>             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
(v7.6.3#76005)