-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.1.0.Alpha1
-
None
The following JIRAs showcase how ass-backwards the implementation of ESB detection/support in as.core's plugin.xml is:
JBIDE-13209
JBDS-2365
JBDS-2394
JBDS-1889
JBDS-2431
Would it be possible to have the various servers simply support 4.x instead of needing to keep updating as.core's plugin.xml every time a new version of ESB 4.x comes out? (4.11 is currently not supported properly, and 4.12 is forthcoming. Can we make this better in JBDS 7, then maybe backport that magic to JBDS 5 and 6?
- is related to
-
JBIDE-13356 ESB 4.12+ support in 3.3.x
- Closed
- relates to
-
JBDS-1889 JBoss ESB runtime check cannot determine correct runtime for SOA-P 5.2.0.ER5 build
- Closed
-
JBDS-2431 JBDS5 - Does not recognize ESB 4.11 - deployments to SOA-P servers fail
- Closed
-
JBDS-2365 ESB projects cannot be deployed using Server Add/Remove
- Closed
-
JBDS-2394 CLONE - ESB projects cannot be deployed using Server Add/Remove
- Closed
-
JBIDE-13209 Need to add ESB 4.12 option with constraints
- Resolved