[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
6:27 p.m.
Nick Boldt created JBIDE-11121:
----------------------------------
Summary: 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
Fix For: 3.3.0.Beta1-soa
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Douglas Palmer updated JBIDE-11121:
-----------------------------------
Fix Version/s: 3.3.0.Beta2-SOA
(was: 3.3.0.Beta1-SOA)
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
Fix For: 3.3.0.Beta2-SOA
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:41 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Douglas Palmer updated JBIDE-11121:
-----------------------------------
Fix Version/s: 3.3.0.Beta3-SOA
(was: 3.3.0.Beta2-SOA)
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
Fix For: 3.3.0.Beta3-SOA
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Douglas Palmer updated JBIDE-11121:
-----------------------------------
Priority: Blocker (was: Major)
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: 3.3.0.Beta3-SOA
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Douglas Palmer updated JBIDE-11121:
-----------------------------------
Fix Version/s: 3.4.x
(was: 3.3.0.Beta3-SOA)
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: 3.4.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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11121:
------------------------------------
For JBT 3.3.x it looks like we need:
graphiti 0.9, emf compare 1.2, bpmn2, bpmn2-modeler, bpel, emf validation, emf validation
ocl, mdt ocl
(based on https://github.com/jboss-switchyard/tools/blob/master/eclipse/pom.xml)
Plus I know Teiid needs uml2. Not sure what else the SOA folk need.
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
7:10 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
The merge platforms Mojo could be used:
https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
It takes as input several target files (defined by GAVs or as reference on local
filesystem), and merge them into a single one that can be deployed using
build-helper-plugin and consumed later.
In that case, we could think of having SOA defining the "last stable core" in a
target-platform, and use the mojo to merge this "core" platform with the JBT
platform. The result would be an SOA Tools platform.
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
4:35 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
On this branch: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121 , I
created an soatools-junoSR1a TP which is made of:
* unified.target +
* Eclipse.org deps for SOA Tools +
* (To be Completed) Reference to some IUs on JBT aggregate site.
Feedback is highly welcome.
[~dpalmer] your opinion on this is important too.
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
6:45 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11121 at 11/19/12 12:44 PM:
---------------------------------------------------------------
Feedback not only welcome, it's REQUIRED.
Particularly from BPEL ([~bbrodt]), Teiid ([~blafond]), Modeshape ([~elvisisking]), Savara
([~objectiser]), and SwitchYard ([~rcernich]).
was (Author: nickboldt):
Feedback not only welcome, it's REQUIRED.
Particularly from BPEL ([~bbrodt]), Teiid ([~blafond]), Modeshape ([~elvisisking], Savara
([~objectiser], and SwitchYard ([~rcernich]).
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
6:45 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11121:
------------------------------------
Feedback not only welcome, it's REQUIRED.
Particularly from BPEL ([~bbrodt]), Teiid ([~blafond]), Modeshape ([~elvisisking], Savara
([~objectiser], and SwitchYard ([~rcernich]).
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
7:05 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Rob Cernich commented on JBIDE-11121:
-------------------------------------
Hey Nick, Mickael,
We're working on putting a process together for handling things like this for SOA
tools.
That said, this looks OK with the following exceptions:
* The guvnor/jbpm entries should be removed
* The bpmn2 modeler need to be from ../site/0.1.0
I have not verified the specific versions of some of the other dependencies (e.g. OCL,
bpel).
Thanks for putting this together.
Rob
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
10:17 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Barry LaFond commented on JBIDE-11121:
--------------------------------------
With our 8.0 Teiid Designer release we've removed our use of UML2 feature and added a
JBoss Server feature.
Here's our current list of dependent features...
* JBossAS Tools
* Data Tools Platform Enablement Extender SDK
* Data Tools Platform Extender SDK
* EMF - Eclipse Modeling Framework SDK
* Graphical Editing Framework GEF SDK
* XSD - XML Schema Definition SDK
* Eclipse Jave Web Developer Tools
* JavaScript Development Tools
* JST Server UI
* WST Server Adapters
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
10:07 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
@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
10:17 a.m.
[
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
11:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-11121 at 11/21/12 5:50 AM:
------------------------------------------------------------------
[~blafond]:Please ignore it.
was (Author: mickael_istria):
[~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")?
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
3:41 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
Using latest commits from that branch, with new stuff into TP + a profile to enable SOA
TP: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121
I could build:
* Teiid, ModeShape using parent and TP from branch and command "mvn verify
-Psoa,maximum -Dno-jbosstools-site"
* Can't build BPEL the same way because it's missing
org.eclipse.bpel.jboss.riftsaw.feature
* Switchyard was built by configuring usage of the target-platform in its pom and then
"mvn verify"
Still not tried savara which looks out-of-sync for parent pom.
To try out locally:
# Clone repo
# checkout JBIDE-11121 branch
# mvn install on target-platforms/soatools-junoSR1a/
# mvn install on parent/
# Use either parent (4.0.0.CR1-SNAPSHOT) with profiles -Psoa,maximum; or use directly TP
org.jboss,tools.target-platforms.soatools-JunoSR1:multiple:4.1.0.JunotSR1a-SNAPSHOT:multiple
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
2:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria edited comment on JBIDE-11121 at 12/5/12 8:45 AM:
-----------------------------------------------------------------
Using latest commits from that branch, with new stuff into TP + a profile to enable SOA
TP: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121
I could build:
* BPEL, Teiid, ModeShape using parent and TP from "JBIDE-11121" branch and
command "mvn verify -Psoa -Dno-jbosstools-site -Dtycho.localArtifacts=ignore
-Dmaven.test.skip"
* Switchyard was built by configuring usage of the target-platform in its pom and then
"mvn verify"
Still not tried savara which looks out-of-sync for parent pom.
To try out locally:
# Clone repo git://github.com/mickaelistria/jbosstools-build.git or add it as a remote on
existing repo
# checkout JBIDE-11121 branch
# mvn install on target-platforms/soatools-4.2.1.a/
# mvn install on parent/
# Use either parent (4.1.0.Alpha1-SNAPSHOT) with profiles -Psoa; or use directly TP
org.jboss,tools.target-platforms.soatools:multiple:4.2.1.a-SNAPSHOT:multiple
was (Author: mickael_istria):
Using latest commits from that branch, with new stuff into TP + a profile to enable
SOA TP: https://github.com/mickaelistria/jbosstools-build/tree/JBIDE-11121
I could build:
* Teiid, ModeShape using parent and TP from branch and command "mvn verify
-Psoa,maximum -Dno-jbosstools-site"
* Can't build BPEL the same way because it's missing
org.eclipse.bpel.jboss.riftsaw.feature
* Switchyard was built by configuring usage of the target-platform in its pom and then
"mvn verify"
Still not tried savara which looks out-of-sync for parent pom.
To try out locally:
# Clone repo
# checkout JBIDE-11121 branch
# mvn install on target-platforms/soatools-junoSR1a/
# mvn install on parent/
# Use either parent (4.0.0.CR1-SNAPSHOT) with profiles -Psoa,maximum; or use directly TP
org.jboss,tools.target-platforms.soatools-JunoSR1:multiple:4.1.0.JunotSR1a-SNAPSHOT:multiple
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
2:50 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
[~bbrodt], [~blafond], [~objectiser], [~elvisisking], [~rcernich], [~dpalmer]: I'd
appreciate to get your feedback soon, since this is something we'll discuss (and
hopefully set up) next week with [~nickboldt] and [~maxandersen]
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
4 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Dan Florian commented on JBIDE-11121:
-------------------------------------
Mickael/Nick: Just ran local build for ModeShape Tools using this command: "mvn clean
install -Psoa" with parent "4.1.0.Alpha1-SNAPSHOT." Worked great and
command is much simpler than before. Then installed MS Tools features using generated
update-site from the build. All looks good. I did *not* have to do steps 1-4 above.
Thanks!
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
4:12 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
[~elvisisking]: how do you know that it's using the suggested soa target platform?
That's why I'd like you to try step 1 to 4, so we are sure you are actually
testing the new SOA target-platform.
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
4:22 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria updated JBIDE-11121:
-----------------------------------
Labels: f2f2012 (was: )
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
9:50 p.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Dan Florian commented on JBIDE-11121:
-------------------------------------
Sorry about that. This time I did do steps 1-4 then did step 5 both ways: (1) "mvn
clean install -Psoa" and (2) "mvn clean install
-Porg.jboss,tools.target-platforms.soatools:multiple:4.2.1.a-SNAPSHOT:multiple."
After the latter I installed into a fresh Eclipse Juno and it all worked fine.
Here is log messages after step step 4:
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ multiple ---
[INFO] Installing
/Users/dan/Temp/soa/jbosstools-build/target-platforms/soatools-4.2.1.a/pom.xml to
/Users/dan/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT.pom
[INFO] Installing
/Users/dan/Temp/soa/jbosstools-build/target-platforms/soatools-4.2.1.a/target/multiple.target
to
/Users/dan/.m2/repository/org/jboss/tools/target-platforms/soatools/multiple/4.2.1.a-SNAPSHOT/multiple-4.2.1.a-SNAPSHOT-multiple.target
Hopefully this is what you needed each of us to do. Let me know if you need anything
else.
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
9:11 a.m.
[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
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
4160
days inactive
4441
days old
jbosstools-issues@lists.jboss.org
22 comments
6 participants
participants (6)
-
Barry LaFond (JIRA) -
Dan Florian (JIRA)
-
Douglas Palmer (JIRA)
-
Mickael Istria (JIRA)
-
Nick Boldt (JIRA)
-
Rob Cernich (JIRA)