[jbosstools-issues] [JBoss JIRA] (JBIDE-10670) JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
@Doug:
The remaining TODO for you here is to implement similar linking for the components in JBT
SOA, so that they too depend on [1] instead of [2].
[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
Then repeat those steps for the _stable_branch jobs (which we'll need in a week after
we freeze) where you'll swap s/trunk/3.3.indigo/ in the URLs [1], [2] noted above.
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
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