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

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick commented on JBIDE-8656:
------------------------------------------

Do we need a SOAIDE component in JIRA to handle SOA tooling JIRAs then?

Even if we go that route, we'd still need one half in JBIDE or JBDS to do the splitting out and the other half in SOAIDE as a related JIRA, wouldn't we?

Or am I caffeine challenged and just not getting what you're proposing here?

> 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: Nick Boldt
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira