[jbosstools-issues] [JBoss JIRA] (JBIDE-10672) include SwitchYard 0.4.0 in JBT SOA Tooling site

[Nick Boldt (JIRA)]

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

Nick Boldt updated JBIDE-10672:
-------------------------------

    Fix Version/s: 3.3.0.CR1
                       (was: 3.3.0.Beta1-soa)


sure you can. Just point both at the same update site via the composite staging site. 

When 0.4.0 releases, you can then have them on different targets. This is what we do w/ Teiid too -- often both these files [1], [2] will point at the same Teiid release.

[1] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/trunk/
[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/3.3.indigo/

The point of having two jobs is that you can have one that builds against upstream stable branch (JBT Beta1) and one that builds against trunk (JBT Beta2 / CR1 / trunk).

But if the second one is not (yet) needed, then we can push this out to CR1.
                
> include SwitchYard 0.4.0 in JBT SOA Tooling site
> ------------------------------------------------
>
>                 Key: JBIDE-10672
>                 URL: https://issues.jboss.org/browse/JBIDE-10672
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, SOA Tooling, SwitchYard
>    Affects Versions: 3.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Douglas Palmer
>             Fix For: 3.3.0.CR1
>
>
> As per comments in SWITCHYARD-623, to add SwitchYard 0.4 to the JBT SOA Tooling aggregate, you must add the new folder [0] to the composite by editing these files [1] so that the SOA Tooling site build can resolve the new content (that is, the switchyard feature listed in site.xml [2] can be found while building:
> [0] http://download.jboss.org/jbosstools/builds/staging/SwitchYard-Tools/
> [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstools/builds/staging/_composite_/trunk/compositeArtifacts.xml, compositeContent.xml
> [2] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/site.xml
> Then, respin this job [3] to verify the site's been updated correctly [4].
> [3] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.aggregate/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/
> Repeat for [5] and [6] -- need a second job for 0.4.0 as it stabilizes for Beta1 inclusion while trunk work continues (eg., toward 0.5.0).
> [5] http://download.jboss.org/jbosstools/builds/staging/SwitchYard-Tools_stable_branch (or equivalent name)
> [6] http://anonsvn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstools/builds/staging/_composite_/3.3.indigo/compositeArtifacts.xml, compositeContent.xml
> You'll then want to add the new job [5] to this view [7].
> [7] https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indigo/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira