Define what should be supported configuration and make it available in docs or some other visible place

[odockal]

As a part of #162 we should have also defined what configuration (servers, runtimes) we are supporting and have it on one place, ie., in readme or in docs if there are such.

[odockal]

I would suggest to have matrix of supported configurations as follows:

• Mapped EAP - WILDFLY servers

Downstream	Upstream	Java Runtime
EAP 7.0	Wildfly 10	1.8
EAP 7.1	Wildfly 11	1.8
EAP 7.2	Wildfly 14	11 & 1.8 / 1.8 (Wildfly 14 does not work with 11 by default)
x	Wildfly 15	11 & 1.8
x	Wildfly 16	11 & 1.8

Also, I would expect adapters to support only latest CDK/Minishift releases (any CRC support planned?).

I do not think it is willing to cover other Wildfly servers and older EAPs, same for AS, right?

[odockal]

Docs to cover the topic:

• Mapping EAP to WildFly
• RH Support policy

[odockal]

We might also take into account that wildfly is a community version of EAP and thus, we may test/support only two latest version or latest supporting java (wf14) 1.8 and newest one.

[odockal]

@robstryker @jeffmaury What do you think?

[robstryker]

I think you guys have covered the docs themselves, but it'd be even more interesting (imo) to expose this via API, so the user can ask the RSP for it's various information, docs, support matrix, etc. That's an interesting idea to me.

[adietish]

@robstryker I dont see in what docs this was covered. Missing something? Nevertheless I believe that also providing this info in API is an excellent idea.

[odockal]

I have the same question. If you mean the link to the docs, I would not suggest to copy docs and support matrix from there, we do not need to have covered support for everything since we are not product yet, right?

Great idea btw...