-
Bug
-
Resolution: Done
-
Major
-
3.3.0.M4
-
None
Because JBoss BPEL was at 0.7.0 in M3, and Eclipse BPEL is at 0.5.0 in M4, there's an install conflict in that users will have to remove 0.7.0 in order to install the updated 0.5.0.
In theory, this means that the Eclipse bits ought to be upversioned to 0.7.0 or later to avoid this - see http://bugs.eclipse.org/362135
For now, BPEL should be removed from the JBT and JBDS SOA Tooling sites while we explore the ultimate solution.
- blocks
-
JBIDE-9646 JBT BPEL is 0.7.0 (old JBoss fork) but JBDS BPEL is 0.5.0 (new Eclipse fork) [was org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name]
-
- Closed
-
- is blocked by
-
JBIDE-10201 associate sites not being loaded correctly into JBT SOA site; duplicate references node in content.xml
-
- Closed
-
- is related to
-
JBDS-1810 Push BPEL editor development back upstream to eclipse.org
-
- Closed
-