[
https://issues.jboss.org/browse/JBIDE-13328?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-13328:
-------------------------------------
It seems there's an interim and private non-api extension point which has been added
recently which allows a module to declare its support for servers, rather than the other
way around. This is progress, but it does not stop the 4.10,4.11,4.12 debacle.
http://git.eclipse.org/c/servertools/webtools.servertools.git/tree/plugin...
as.core plugin should understand the idea of ESB 4.x instead of
needing to explicitly list versions like 4.8,4,9,4.10,4.11,4.12
-------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13328
URL:
https://issues.jboss.org/browse/JBIDE-13328
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Rob Stryker
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?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira