[jbosstools-issues] [JBoss JIRA] (JBDS-2536) JBDS70_0317: [Commit] (Dev) (P2) Signed Jars of all org.jboss / com.jboss features & plugins

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784391#comment-12784391 ] 

Nick Boldt commented on JBDS-2536:
----------------------------------

Tests here [1] indicate we can use 2009 key, but we are currently limited to building on a SINGLE SLAVE if we want to perform signing. 

[1] https://issues.jboss.org/browse/JBIDE-13407?focusedCommentId=12783711&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-12783711

We would need to get rpm-sign installed on all the slaves if we want to realistically be able to sign jars as part of the CI builds. Is this something to push on now, or to wait for 7.1?
                
> JBDS70_0317: [Commit] (Dev) (P2) Signed Jars of all org.jboss / com.jboss features & plugins
> --------------------------------------------------------------------------------------------
>
>                 Key: JBDS-2536
>                 URL: https://issues.jboss.org/browse/JBDS-2536
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Requirements
>    Affects Versions: 7.0.0.GA
>            Reporter: Jiri Pallich
>            Assignee: Nick Boldt
>            Priority: Critical
>              Labels: dropcandiate
>             Fix For: 7.0.0.CR1
>
>
> Avoids "you're installing unsigned content. do you wish to proceed?" warning during installation
> See https://issues.jboss.org/browse/JBIDE-13407 for details / screenshot

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira