[
https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin....
]
Martin Malina commented on JBDS-3431:
-------------------------------------
[~mhusnain], I believe the conclusion here was to use EAP 6.x for JBDS 8.0 and 8.1,
instead of listing EAP 6.0, 6.1, 6.2, 6.3, 6.4. Can you use that?
But I have one concern here. [~mmusaji], you say we can't say JBDS 6 supports EAP 6.x
now, because EAP 6.4 will surely not work (there were some changes in EAP 6.1 requiring a
new server adapter). But isn't that exactly what we're doing with JBDS 8 now? We
will say we support JBDS 8.1 with EAP 6.x. But then if hypothetically there is EAP 6.5
that requires some changes a year from now when JBDS 9 is already out, saying JBDS 8.1
supports EAP 6.x will no longer be true. But perhaps we can deal with such situation if it
really happens. Another possibility is to use .x only for currently newest versions and
once we have a new version, we can retrospectively specify the exact version numbers for
JBDS 8.1 to reflect the reality at the time.
Update JBDS support matrix to include only major version of EAP
---------------------------------------------------------------
Key: JBDS-3431
URL:
https://issues.jboss.org/browse/JBDS-3431
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: documentation
Affects Versions: 8.1.0.GA
Reporter: Mustafa Musaji
Assignee: Misha Ali
Update this page
https://access.redhat.com/articles/427493
So that we only include the major versions of EAP supported
I.e. 4.x, 5.x and 6.x
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)