It should not require a new AS/EAP release to get a console that can handle extensions provided by non-AS/EAP layers or add-ons.

To ensure this the AS needs to support both of the following:

1) Distributing the console as a separate layer so we can have a separate release stream to pick up new console releases that include new extensions.
2) Distributing the console as a module included with each layer or add-on, with the AS able to determine which of the available console modules is the most recent version and load it.

The former is a natural fallout of the parent task and requires no further work in the AS itself.

The latter is a new capability.

It is not a requirement for community AS 7.2 that we choose which approach will be followed when layered products are produced. However, we will need to settle that issue before EAP 6.1 is finalized.