[
https://jira.jboss.org/jira/browse/JBIDE-5898?page=com.atlassian.jira.plu...
]
Nick Boldt commented on JBIDE-5898:
-----------------------------------
To solve the bpel conflict, you have to install the bpel SDK on top of the existing bpel
SDK. You cannot simply update the runtime w/o updating the SDK feature. This is p2 being
p2 and there's nothing that we can do from the release side of things to fix this.
Alternatively, uninstall the existing BPEL SDK feature, then install the new BPEL runtime
feature.
To solve the jbpm issue, uninstall the old jbpm features before installing the new
version. This problem arises because of the way the features are encoded to not permit 4.3
to be a valid update for 4.0, and the fragile dependency of jbpm3 and jbpm4 on their
jbpm.common feature.
jBPM conflicts during update from 3.1.0 CR1 to CR2
--------------------------------------------------
Key: JBIDE-5898
URL:
https://jira.jboss.org/jira/browse/JBIDE-5898
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.1.0.CR2
Environment: From JBT 3.1.0 CR1 H192 to CR2 build 268
Reporter: Jiri Peterka
Assignee: Nick Boldt
Priority: Blocker
Fix For: 3.1.0.CR2
Attachments: bpel-conflict.png, update-cr1-to-cr2.png
Steps:
1. Have CR1 JBT installation
2. Download JBT 3.1.0. CR2
3. Select all components
4. Try to install
ERROR: jBPM conflicts, see screenshot
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira