[jbosstools-issues] [JBoss JIRA] (JBTIS-2) ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBTIS-2:
--------------------------------

New job to publish nightlies to integration:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbtis-4.0_stable_branch.components-publish.matrix/

Results are here:

http://download.jboss.org/jbosstools/updates/integration/juno/integration-stack/
                
> ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-2
>                 URL: https://issues.jboss.org/browse/JBTIS-2
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/.
> This issue should be a container for child issues assigned to each project's releng person.
> Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits:
> * JBIDE-12220 create generic publishing job which takes as input three parameters 
> Done:
> * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/switchyard/0.5.0.Final/
> * Modeshape Tools - JBBUILD-720, MODE-1506
> *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/modeshape/ and 
> *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/modeshape/
> Publishes elsewhere, manually symlinked:
> * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/droolsjbpm/5.4.0.Final/
> Publishes elsewhere:
> * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/
> * pi4soa - http://pi4soa.sourceforge.net/updates/
> Publishes as zip only:
> * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_designer-7.7.0.v20120410-1918-H1074-Final.zip/download
> No publishing or archiving strategy (staging only):
> * SOA Runtime Detection - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--runtime-soa/all/repo/ 
> * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--esb/all/repo/ 
> * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--jbpm/all/repo/ 
> --> see also https://issues.jboss.org/browse/JBIDE-12631
> * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk.component--bpel/all/repo/ 
> ---
> Once all the components are publishing sites, they can 
> a) easily link to those individual sites from their download pages on www.jboss.org/{projectname}
> b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/
> c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies
> d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS 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