[
https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
Thanks Mickael. I would like to try and do this myself to get a
better understanding of what's going on here...
Ok, great!
So, I need to...
Those more recent instructions are better:
{quote}
If you're using JBT parent pom
1. change parent pom version to 4.1.0.JBIDE-11121-SNAPSHOT
2. run "mvn clean verify -P soa -Dno.jbosstools.site
-Dtycho.localArtifacts=ignore"
{quote}
Then please post logs and tell us if it's working.
Please do not change Eclipse projects (BPEL and BPMN). Those project must remain
independent from JBoss Tools. This only applies to JBoss Tools BPEL or other Tooling
component at
JBoss.org you're working on.
This target-platform is only meant to be helpful to JBoss Projects. Seen from JBoss
projects, Eclipse BPEL and BPMN are independent components, than we retrieve as any
Eclipse.org dependency.
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