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

[Paul Richardson (JIRA)]

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

Paul Richardson commented on JBIDE-11121:
-----------------------------------------

Have started using this target as the foundation for the teiid-designer.target and works nicely for the project.

http7://github.com/Teiid-Designer/teiid-designer/blob/master/target-platform/pom.xml

Just want to give the thumbs up from our side and subject to approval, it would be good for it to be merged into master.

Thanks

phantomjinx
                
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11121
>                 URL: https://issues.jboss.org/browse/JBIDE-11121
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: SOA Tooling
>    Affects Versions: 3.3.0.Beta1-SOA
>            Reporter: Nick Boldt
>            Assignee: Douglas Palmer
>            Priority: Blocker
>              Labels: f2f2012
>             Fix For: 4.0.0.Alpha1-SOA
>
>         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