Nick Boldt added a comment - 21/Oct/11 8:22 PM To facilitate this work, I've tossed a few patches at the BPMN2 modeler project @ eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=361714 https://bugs.eclipse.org/bugs/show_bug.cgi?id=361715 https://bugs.eclipse.org/bugs/show_bug.cgi?id=361716

Max Rydahl Andersen added a comment - 24/Oct/11 3:18 AM Those tycho patches is just for bpmn2 to build their updatesite easily and then we mirror their work into our dependencies or ?

Nick Boldt added a comment - 24/Oct/11 11:03 AM They're to move bpmn2-modeler project up to using Tycho 0.13, fixing source gen, and including their upstream deps in the metadata for their update site so that users can more easily install it. Does not solve downstream issues for us; for that I'll still have to mirror their work (as you say) onto download.jb.org along w/ the rest of the Eclipse.org stuff, and stick their bits into our Indigo mirror ( http://download.jboss.org/jbosstools/updates/indigo/SR1/ ) This is starting to feel like a Beta1 thing more than an M4 thing. Assigning to Bob so he gets email about this

Nick Boldt added a comment - 24/Oct/11 1:56 PM OK, so we now have bits built in https://hudson.eclipse.org/hudson/job/tycho-bpmn2modeler-0.0.1-nightly/86/ and in http://download.eclipse.org/bpmn2-modeler/site/ . Next... I need to mirror this onto http://download.jboss.org/jbosstools/updates/requirements/ ?

Nick Boldt added a comment - 24/Oct/11 9:36 PM - edited What features/plugins need to be in JBDS 5? So far, in the SOA Tooling site for JBDS 5.0M4 ( http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable_branch.soa-tooling.updatesite/product-soa/ ), we only have these 4: features/com.jboss.jbds.bpel.feature_1.1.0.v20111022-1053-H63-M4.jar features/org.jboss.tools.bpel.feature_1.1.0.v20111022-0856-H31-M4.jar plugins/com.jboss.jbds.bpel.examples_1.0.0.v20111022-1053-H63-M4.jar plugins/org.jboss.tools.bpel.runtimes_0.5.0.v20111022-0856-H31-M4.jar I suspect that's wrong, however, as there's no bpmn stuff in the site.

Nick Boldt added a comment - 25/Oct/11 6:15 PM Meanwhile... in JBoss Tools 3.3.0.M4, after installing the BPEL feature from http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M4.soa-tooling/ , we get this: org.jboss.tools.bpel.feature_1.1.0.v20110831-2238-H14-M3   org.eclipse.bpel.apache.ode.deploy.model_0.6.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.apache.ode.deploy.ui_0.7.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.common.model_0.6.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.common.ui_0.6.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.wsil.model_0.6.0.v20110831-2238-H14-M3 org.eclipse.bpel.validator_0.7.0.v20110831-2238-H14-M3 org.jboss.tools.bpel.cheatsheet_1.1.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.model_0.7.0.v20110831-2238-H14-M3.jar org.jboss.tools.bpel.runtimes_0.5.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.xpath10_0.6.0.v20110831-2238-H14-M3.jar org.eclipse.bpel.ui_0.7.0.v20110831-2238-H14-M3 Then, after installing the two Savara features, we get these additional files: org.jboss.savara.tools.feature_2.0.0.20111018-M5 org.savara.tools.feature_2.0.0.20111018-M5   org.pi4soa.scenario_3.1.1.v20111018-0306-H157-M4.jar org.pi4soa.designer_3.1.1.v20111018-0306-H157-M4 org.pi4soa.cdl_3.1.1.v20111018-0306-H157-M4 org.savara.activity_2.0.0.20111018-M5.jar org.pi4soa.scenario.designer_3.1.1.v20111018-0306-H157-M4.jar org.savara.common_2.0.0.20111018-M5.jar org.savara.contract_2.0.0.20111018-M5.jar org.savara.bpel_2.0.0.20111018-M5.jar org.savara.monitor_2.0.0.20111018-M5.jar org.savara.bpmn2_2.0.0.20111018-M5.jar org.savara.pi4soa.cdm_2.0.0.20111018-M5.jar org.savara.protocol_2.0.0.20111018-M5.jar org.savara.scenario.simulator.cdm_2.0.0.20111018-M5.jar org.savara.scenario_2.0.0.20111018-M5.jar org.savara.switchyard.bpel_2.0.0.20111018-M5.jar org.savara.tools.bpel_2.0.0.20111018-M5.jar org.savara.tools.bpmn2_2.0.0.20111018-M5.jar org.savara.tools.common_2.0.0.20111018-M5.jar org.savara.tools.sca.java_2.0.0.20111018-M5.jar org.savara.tools.scenario_2.0.0.20111018-M5.jar org.pi4soa.service_3.1.1.v20111018-0306-H157-M4 org.savara.tools.validator_2.0.0.20111018-M5.jar org.savara.tools.switchyard.bpel_2.0.0.20111018-M5.jar org.savara.tools.wsdl_2.0.0.20111018-M5.jar org.savara.wsdl_2.0.0.20111018-M5.jar org.scribble.common_2.0.0.CR2.jar org.scribble.protocol.export.monitor_2.0.0.CR2.jar org.scribble.protocol_2.0.0.CR2.jar org.scribble.protocol.monitor_2.0.0.CR2.jar org.scribble.protocol.projection_2.0.0.CR2.jar org.savara.scenario.simulator.sca_2.0.0.20111018-M5.jar org.scribble.protocol.parser_2.0.0.CR2.jar org.savara.sca.java_2.0.0.20111018-M5.jar So... not sure if there's something missing since in neither case is graphiti or bpmn2 stuff installed. Closest we get are these: org.savara.bpmn2_2.0.0.20111018-M5.jar org.savara.tools.bpmn2_2.0.0.20111018-M5.jar and org.eclipse.gef_3.7.1.v20110830-1143-777D181B3Bz06C853D8863365 (feature) org.eclipse.gef_3.7.1.v20110830-1143.jar (plugin)

Robert (Bob) Brodt added a comment - 26/Oct/11 12:59 PM - edited According to Gary: "Savara tooling is not in JBDS currently, so shouldn't be an issue. In terms of the project/jbt, it is used in Savara to display the generated BPMN2 models. Eventually it will be used to create choreographies, instead of using WS-CDL." so...the missing bpmn2 modeler and graphiti deps is a non-issue. Gary, can you confirm ?