You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2017/05/28 16:42:04 UTC

[jira] [Resolved] (POLYGENE-115) JAR Signing

     [ https://issues.apache.org/jira/browse/POLYGENE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niclas Hedhman resolved POLYGENE-115.
-------------------------------------
    Resolution: Won't Fix
      Assignee: Niclas Hedhman

I never saw this taking off at ASF, and I am uncertain about its current status. Closing it to keep our JIRA clean.

> JAR Signing
> -----------
>
>                 Key: POLYGENE-115
>                 URL: https://issues.apache.org/jira/browse/POLYGENE-115
>             Project: Polygene
>          Issue Type: Improvement
>            Reporter: Paul Merlin
>            Assignee: Niclas Hedhman
>              Labels: build, release, signature
>
> bq. That infrastructure now exists through code signing service by Symantec. One PMC member (or more) gets their own unique log in, pushes the artifact (.jar, in this example) to the service and is returned a signed artifact reflecting the ASF providence.
> See the Incubator discussion http://markmail.org/message/lsf6px4tmfqnjlvf
> See the Zest discussion http://zest.markmail.org/thread/ae3clozosid7oz3v



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