[jbosstools-issues] [JBoss JIRA] (JBIDE-8656) Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-8656:
-----------------------------------

With the exception of the idea of having a new SOA Tooling site on jboss.org (independent of the Core stuff in jboss.org/tools), which IIRC was nixed a while back, the subtasks and dependent issues in this JIRA are all done.

Doug, I think you can close this issue.
                
> Split SOA components out of JBoss Tools aggregate site; create 2nd aggregate for SOA Tooling
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-8656
>                 URL: https://issues.jboss.org/browse/JBIDE-8656
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: BPEL, bpm, drools, esb, jbpm, modeshape, smooks, teiid
>    Affects Versions: 3.3.0.M1
>            Reporter: Nick Boldt
>            Assignee: Douglas Palmer
>             Fix For: 3.3.0.Beta1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> The following components should be aggregated in a NEW aggregate build and removed from the existing one:
> Drools 5.2
> Flow/jBPM
> BPMN2 (there is no JIRA component for this yet)
> BPEL (moving to Eclipse.org)
> Teiid
> Modeshape
> ESB
> -Smooks-
> 1. Fix ~/trunk/build/aggregate/ - remove components from site.xml
> 2. Create new ~/trunk/build/aggregate-soa/ - add components to site.xml
> 3. Create new http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.aggregate-soa/ (or similar)
> 4. get new www.jboss.org/soatools/ site, publish there instead of www.jboss.org/tools/, and cross link project pages.

--
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