[
https://issues.apache.org/jira/browse/SLING-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059554#comment-16059554
]
Robert Munteanu commented on SLING-6585:
----------------------------------------
Here's one possible way of solving this:
# Write the maven plugin that performs the signing
# Use the
[tycho-p2-extras-plugin|https://wiki.eclipse.org/Tycho/Additional_Tools#tycho-p2-extras-plugin]
to:
## mirror the source repository to another directory ( {{mirror}} goal )
## rebuild the p2 metadata ( {{publish-features-and-bundles}} goal )
# Use the antrun-maven-plugin to copy other files from the source directory (
index.html, p2.inf, etc )
> 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.4.14#64029)
