[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:comment-tabpanel&focusedCommentId=12783680#comment-12783680 ] 

Nick Boldt commented on JBIDE-13407:
------------------------------------

Tests indicate that the signing is only happening for plugins that Tycho's actually building, not aggregating. So, we would have to define two settings for all jobs:

# -PsignAndPack200
# <assignedNode>dev01-rhel5-x86</assignedNode> (only node w/ signing enabled so far)

Experimenting w/ a Base build (bottom of the stack) to sign those plugins; seems like com.jboss.jbds plugins ARE signed and there's no prompt re: accepting the cert.

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base.signed_master/
                
> 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.Final, 4.0.0.Final, 4.1.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.2.0.Alpha1
>
>         Attachments: dialog_do-you-trust-these-certs.png, JBDS6-STS272-install-from-central-Unsigned-Content-Warning.png, no-more-jboss-unsigned-content-but-what-about-org.sonatype.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