[ https://issues.jboss.org/browse/JBDS-2123?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2123: ----------------------------- Fix Version/s: 5.0.0.Beta1-SOA (was: 5.0.0.Beta3) Assignee: Douglas Palmer (was: Snjezana Peco) Affects Version/s: 5.0.0.Beta1-SOA (was: 5.0.0.Beta3) Component/s: SOA Tooling / Platform updatesite Please assign SOA issues to Doug Palmer, and to the *-SOA version targets. This is for 5.0.0.Beta1-SOA. -- 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

[ https://issues.jboss.org/browse/JBDS-2123?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2123 at 5/7/12 11:08 AM: ----------------------------------------------------------- First issue - flow: !SOA-PInstall.png! Second issue - bpel: !soa-p-tooling-cannot-install-bpel-missing-eclipse.org-plugin.png! was (Author: nickboldt): Further problem: !soa-p-tooling-cannot-install-bpel-missing-eclipse.org-plugin.png! -- 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

[ https://issues.jboss.org/browse/JBDS-2123?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2123: ---------------------------------- With BPEL installed from SOA site directly, i get this error instead: {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss ESB Tools 1.5.0.v20120427-1932-H1-Beta1-SOA (org.jboss.tools.esb.feature.feature.group 1.5.0.v20120427-1932-H1-Beta1-SOA) Missing requirement: JBoss ESB Project UI Plugin 1.5.2.v20120427-1932-H1-Beta1-SOA (org.jboss.tools.esb.project.ui 1.5.2.v20120427-1932-H1-Beta1-SOA) requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found Cannot satisfy dependency: {code} So... I think we need to composite in the JBDS Core/TP site into the JBDS SOA Site to solve missing upstream deps. working on a fix... -- 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

[ https://issues.jboss.org/browse/JBDS-2123?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2123 at 5/7/12 1:18 PM: ---------------------------------------------------------- https://devstudio.jboss.com/updates/5.0/staging/soa-tooling/ updated to include ../ site (which in turn includes latest JBDS Core & TP sites). Also removed flow.feature from central connector in trunk (but NOT in soatools beta1 branch) because jbpm3 does not need it - IIRC that's just for jbpm4. was (Author: nickboldt): https://devstudio.jboss.com/updates/5.0/staging/soa-tooling/ updated to include ../ site (which in turn includes latest JBDS Core & TP sites). Also removed flow.feature from central connector because jbpm3 does not need it - IIRC that's just for jbpm4. -- 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

[ https://issues.jboss.org/browse/JBDS-2123?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2123: ------------------------------- Fix Version/s: 5.0.0.Beta2-SOA (was: 5.0.0.Beta1-SOA) Priority: Blocker (was: Major) Changed fix-in version to SOA-beta2 and and raised severity to blocker - we will verify this in the next tooling build. The workaround is to add an update site for: https://devstudio.jboss.com/updates/5.0/staging/ -- 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