[
https://issues.jboss.org/browse/JBTIS-1?page=com.atlassian.jira.plugin.sy...
]
Nick Boldt commented on JBTIS-1:
--------------------------------
Based on what I see here [0], your Juno-based target platform requires:
Graphiti 0.9.1
Guava 10.0.1 (from Orbit R20120526062928)
OCL 4.0.1
EMF Compare 1.3.2 -> requires EMF 2.8
EMF Query OCL 1.6 -> requires EMF 2.8, OCL 4.0, UML2 4.0
All of which is included in here [1].
As well as:
BPMN2 0.7.0 and BPMN2 Modeler 0.1.0 [2]
BPEL 1.0.2 [3]
and of course...
JBT 4.0
JBT Tests 4.0
---
Questions:
1.
EMF Compare 1.3 is only compatible w/ Eclipse 3.8, not 4.2 [4]. What depends on this, and
can version 2.0 be used instead, which works w/ Eclipse 3.8 AND with 4.2? Or
2.
UML2 4.0 is not in your TP, though if I recall correctly (and they haven't removed the
requirement) Teiid Designer requires UML2. Should it be added to your TP? I suspect
you're resolving that dependency because it's already included in the JBT target
platform [5] ? If that's the case then I believe it should be removed from ours and
added to yours instead.
3.
Graphiti 0.9 is in both your TP and the JBT one [5], yet I don't think anything in JBT
requires it. It was most likely added to support something in the SOA-P/BRMS tooling space
before you started having your own TP. It too should probably be removed from ours in
favour of it being in yours - no need to be in both.
Observation:
1.
I've added a mirror on
download.jboss.org for the only requirement I saw above
that's not already there - the older version of the bpmn2 stuff, now mirrored here
[2]. As such, you should be able to have all the URLs in your TP point to
download.jboss.org URLs instead of the 8
eclipse.org ones, and get better performance when
building the target platform site. You can even simplify the TP since of those 8 URLs, 6
can be collapsed down into a single one [1], leaving only BPEL and BPMN2 as separate
entries, followed by the JBoss Tools stuff.
--
[0]
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/pleacu-jbosstools-in...
[1]
http://download.jboss.org/jbosstools/updates/requirements/juno/2012092809...
[2]
http://download.jboss.org/jbosstools/updates/requirements/bpmn2-modeler/2...
*NEW*
[3]
http://download.jboss.org/jbosstools/updates/requirements/bpel/1.0.2.v201...
[4]
http://wiki.eclipse.org/EMF_Compare#Compatibility
[5]
http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/
Generate target platforms for JBT/JBDS SOA Tooling which include:
JBT/JBDS Core TP + last stable Core milestone
---------------------------------------------------------------------------------------------------------------
Key: JBTIS-1
URL:
https://issues.jboss.org/browse/JBTIS-1
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Reporter: Nick Boldt
Assignee: Paul Leacu
Labels: f2f2012
Attachments: JBIDE-11121.tweak.txt, 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