-
Bug
-
Resolution: Done
-
Critical
-
3.3.0.Beta1-SOA
-
None
-
eclipse-jee-indigo-SR2-RC3-linux-gtk-x86_64
http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.core/
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64)
OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode)Red Hat Enterprise Linux Workstation release 6.2 (Santiago)
eclipse-jee-indigo-SR2-RC3-linux-gtk-x86_64 http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.Beta3.core/ java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) (rhel-1.43.1.10.6.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b11, mixed mode) Red Hat Enterprise Linux Workstation release 6.2 (Santiago)
The build path for these ESB 5.0 quickstarts is incorrect when JBT is used with an SOA-P 5.3.0.ER2 server. The build path does not find the EAP runtime in that SOA-P server.
The other quickstarts look OK - and this problem is not being seen on JBDS 5.0.0.beta3
See the attached screenshots for an illustration.
