Reputation: 965
Again, no information is available about this on any Red Hat or JBoss site, so I ask it here...
I am not sure if it is 13 or 14.
Upvotes: 2
Views: 7510
Reputation: 7583
Mapping the Community versions with JBoss EAP versions
It is not possible to map exactly a version of the Community version (JBoss EAP, WildFly) with the corresponding version of the supported version (JBoss EAP) as they are maintained in separated branches. In general terms, the following tables summarizes the version of WildFly used as baseline for a JBoss EAP version:
JBoss EAP Version WildFly Version
Upvotes: 6
Reputation: 868
The versions of JBoss EAP are forked from the Wildfly projects, when certain features are complete enough they fork the project and create an EAP version.
JBoss EAP 7.0 is forked from WildFly 10
JBoss EAP 7.1 is forked from a working branch of WildFly 11
JBoss EAP 7.2 unfortunatelly has no oficial information available yet as you can see here, here and here - but I do believe it's forked from Wildfly 13 or 14, considering the last fork was Wildfly 11 and we are 3 versions ahead now.
And here is a comparative with some new information.
Upvotes: -1
Reputation: 21
I believe that it is forked from WF 13.
If you look at the module for the server core, you'll see that WF 13 uses WildFly Core 5.0.0.Final. EAP 7.2 Beta uses WildFly Core 5.0.5.
If you look at WF 14, it uses WildFly Core 6.0.2.Final, so EAP 7.2 is definitely not forked from this.
You can see the module used for the server core at: eap-install-dir/modules/system/layers/base/org/jboss/as/server/main
Upvotes: 1