[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-11121 at 11/21/12 4:16 AM:
------------------------------------------------------------------
[~blafond]: I've successfully built Teiid Designer without having JBossAS Tools in the
target-platform. Is this a "static" dependency? Or is it a runtime requirement?
If it is a runtime requirement, is it made explicit in your features (usign a
"requires")?
was (Author: mickael_istria):
@Barry: I've successfully build Teiid Designer without having JBossAS Tools in the
target-platform. Is this a "static" dependency? Or is it a runtime requirement?
If it is a runtime requirement, is it made explicit in your features (usign a
"requires")?
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