[jbosstools-issues] [JBoss JIRA] (JBIDE-13407) Jar signing for JBT plugins/features

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-13407:
-------------------------------

    Attachment: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png


When installing something like STS 2.7.2 (with our patch) from JBDS 6 Central, user is prompted to accept the fact that unsigned content will be installed.

Same warning appears for all JBDS SOA/BRMS stuff, and anything from jboss.org (JBT, JBDS BYOE) installed from Eclipse Marketplace... because as yet we don't sign our content.

!JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png!
                
> Jar signing for JBT plugins/features
> ------------------------------------
>
>                 Key: JBIDE-13407
>                 URL: https://issues.jboss.org/browse/JBIDE-13407
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, updatesite
>    Affects Versions: 3.3.2, 4.0.0.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.1.0.Alpha1
>
>         Attachments: JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png
>
>
> Investigate jar signing processes/options and locations of certs we can use for signing of JBIDE / JBTIS community jars for repackaging into JBDS product.
> Goal is to avoid seeing warning about installing unsigned content from Eclipse Marketplace, p2 installer, or JBoss Central.

--
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