[jbosstools-issues] [JBoss JIRA] (JBIDE-10670) JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-10670:
---------------------------------------------

what I dont get is why we can't have SOA builds just depend on aggregate site and integrate often that way ?

Building of latest milestone is fine for non-development-cycles, but that isn't where we are at now.
                
> 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