[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-11121:
-------------------------------
Attachment: JBIDE-11121.tweak.txt
I think this patch might help things, but I still can't resolve the TP, whether
it's called soatools-JunoSR1a or soatools, and whether the parent pom is versioned
4.1.0.Alpha1-SNAPSHOT or 4.1.0.JBIDE-11121-SNAPSHOT:
[^JBIDE-11121.tweak.txt]
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