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

[Mickael Istria (JIRA)]

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

Mickael Istria edited comment on JBIDE-11121 at 12/5/12 8:45 AM:
-----------------------------------------------------------------

Using latest commits from that branch, with new stuff into TP + a profile to enable SOA TP: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121
I could build:
* BPEL, Teiid, ModeShape using parent and TP from "JBIDE-11121" branch and command "mvn verify -Psoa -Dno-jbosstools-site -Dtycho.localArtifacts=ignore -Dmaven.test.skip"
* Switchyard was built by configuring usage of the target-platform in its pom and then "mvn verify"

Still not tried savara which looks out-of-sync for parent pom.

To try out locally:
# Clone repo git://github.com/mickaelistria/jbosstools-build.git or add it as a remote on existing repo
# checkout JBIDE-11121 branch
# mvn install on target-platforms/soatools-4.2.1.a/
# mvn install on parent/
# Use either parent (4.1.0.Alpha1-SNAPSHOT) with profiles -Psoa; or use directly TP org.jboss,tools.target-platforms.soatools:multiple:4.2.1.a-SNAPSHOT:multiple
                
      was (Author: mickael_istria):
    Using latest commits from that branch, with new stuff into TP + a profile to enable SOA TP: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121
I could build:
* Teiid, ModeShape using parent and TP from branch and command "mvn verify -Psoa,maximum -Dno-jbosstools-site"
* Can't build BPEL the same way because it's missing org.eclipse.bpel.jboss.riftsaw.feature
* Switchyard was built by configuring usage of the target-platform in its pom and then "mvn verify"

Still not tried savara which looks out-of-sync for parent pom.

To try out locally:
# Clone repo
# checkout JBIDE-11121 branch
# mvn install on target-platforms/soatools-junoSR1a/
# mvn install on parent/
# Use either parent (4.0.0.CR1-SNAPSHOT) with profiles -Psoa,maximum; or use directly TP org.jboss,tools.target-platforms.soatools-JunoSR1:multiple:4.1.0.JunotSR1a-SNAPSHOT:multiple
                  
> 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
>             Fix For: 4.0.x
>
>
> 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