[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)
jira-events at lists.jboss.org
Thu Dec 6 03:11:22 EST 2012
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739844#comment-12739844 ]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
No problem, Dan.
Your use case just shows that I should find a more direct way for you to test. I've worked on something simpler, can you please *ALL* give it a try asap?
Just follow *exactly* those instructions:
If you're using JBT parent pom
# change parent pom version to 4.1.0.JBIDE-11121-SNAPSHOT
# run "mvn clean verify -P soa -Dno.jbosstools.site -Dtycho.localArtifacts=ignore"
If you're *not* using JBT parent:
# Remove/comment from your pom all <repositories> and target-platform-definition-configuration
# put in your pom.xml:
{code:xml}
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tychoVersion}</version>
<configuration>
<target>
<artifact>
<groupId>org.jboss.tools.target-platforms.${tpc.group}</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<classifier>multiple</classifier>
</artifact>
</target>
</configuration>
</plugin>
{code}
# Run a "mvn clean verify"
Please post your build log there.
> 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.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
More information about the jbosstools-issues
mailing list