Today the master branch is treated as a catalog of shared modules. This approach seems to show some limitations (we have a lot of useless modules with code duplication) when the goal is to create a “product” from the modules. The modules are not really re-usable outside a given EAP release. As opposed to cct_module that is a pure catalog of modules with version driven by cekit module version, we are driven by product (EAP, CD, ..) versions.

We plan to create a 1.0.x branch from the master branch of https://github.com/jboss-container-images/jboss-eap-modules. This "legacy" branch will be used to create CD18 built from the zip file (legacy way). It is the backward compatible branch. To be used by layered products.

Once https://github.com/wildfly/temp-eap-modules EAP7-1216 is merged into master we will do a cleanup of master:

• Remove all un-used modules (and un-used module versions).
• The set of modules to keep are the ones referenced by: https://github.com/wildfly/temp-openshift-image/blob/EAP7-1216/image.yaml. We should remove more than 90% of the existing modules. A lot of them have been moved to: https://github.com/wildfly/wildfly-cekit-modules
• python2 and python3 related modules are kept.
• Remove all behave feature files for released versions (6, 7.1, 7.2 features).
• Move tests/7/*.features to tests/ directory.