[jbosstools-issues] [JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
Hey Bob.
The target-platform (defined by a .target file) is the way how Tycho will resolve
dependencies. We are trying to use a target-platforms that is based on JBoss Tools
target-platform, to ensure the SOA/Integration components are compatible with JBoss Tools
and then that all JBoss Eclipse stuff can be installed together.
So I've made a target-platform that I hope should work for your SOA projects.
If you feel a bit lost with that, can you please tell me where I can get your code, so
I'll give it a try.
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
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