[jbosstools-issues] [JBoss JIRA] (JBTIS-1) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone

[Paul Leacu (JIRA)]

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

Paul Leacu resolved JBTIS-1.
----------------------------

    Fix Version/s: 4.0.0
       Resolution: Done


complete: see 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-target-platform/
https://github.com/jbosstools/jbosstools-integration-stack/tree/master/target-platform/
                
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTIS-1
>                 URL: https://issues.jboss.org/browse/JBTIS-1
>             Project: JBoss Tools Integration Stack
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>            Reporter: Nick Boldt
>            Assignee: Paul Leacu
>              Labels: f2f2012
>             Fix For: 4.0.0
>
>         Attachments: JBIDE-11121.tweak.txt, ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone. 
> 2. JBDS Core TP + last stable JBDS Core milestone. 
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira