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

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-11121 at 12/13/12 5:10 PM:
--------------------------------------------------------------

I think some steps might be missing. Here's what I did:

{code}
git clone git://github.com/jbosstools/jbosstools-maven-plugins/
pushd jbosstools-maven-plugins/tycho-plugins/; mvn install; popd

git clone git://github.com/mickaelistria/jbosstools-build.git
pushd jbosstools-build; git checkout JBIDE-11121
pushd parent; mvn install; popd
pushd target-platforms/jbosstools-4.2.1.a/; mvn install; popd
pushd target-platforms/soatools-4.2.1.a/; mvn install; popd

git clone git://github.com/jbosstools/jbosstools-bpel.git
pushd jbosstools-bpel
sed -i -e "s/4.1.0.Alpha1-SNAPSHOT/4.1.0.JBIDE-11121-SNAPSHOT/g" pom.xml 
mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore
popd
{code}

Result:

{code}

[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ multiple ---
[INFO] Installing /home/nboldt/tru/jbosstools-build/target-platforms/soatools-4.2.1.a/pom.xml to /home/nboldt/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT.pom
[INFO] Installing /home/nboldt/tru/jbosstools-build/target-platforms/soatools-4.2.1.a/target/multiple.target to /home/nboldt/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT-multiple.target

> mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore

Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT

> mvn clean verify -P soa -Dno.jbosstools.site 

Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT

> mvn clean verify -P soa

Could not resolve target platform specification artifact org.jboss.tools.target-platforms.soatools-JunoSR1a:multiple:target:multiple:4.2.1.a-SNAPSHOT

{code}

So... not sure what I'm doing wrong but I can't seem to resolve the new soatools TP definition.
                
      was (Author: nickboldt):
    I think some steps might be missing. Here's what I had to do... or at least I *assume* this will work. Had to shut down laptop while jbosstools-4.2.1.a tp build was running:

{code}
git clone git://github.com/jbosstools/jbosstools-maven-plugins/
pushd jbosstools-maven-plugins/tycho-plugins/; mvn install; popd

git clone git://github.com/mickaelistria/jbosstools-build.git
pushd jbosstools-build; git checkout JBIDE-11121
pushd parent; mvn install; popd
pushd target-platforms/jbosstools-4.2.1.a/; mvn install; popd
pushd target-platforms/soatools-4.2.1.a/; mvn install; popd

git clone git://github.com/jbosstools/jbosstools-bpel.git
pushd jbosstools-bpel
sed -i -e "s/4.1.0.Alpha1-SNAPSHOT/4.1.0.JBIDE-11121-SNAPSHOT/g" pom.xml 
mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore
popd
{code}

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