Today all feature-packs WildFly Glow is discovering are put at the same level with respect to their maturity level. That is not reflecting the WildFly feature process in which some feature-packs could be incubating prior to reach the right stability level.
WildFly Glow should separate these feature-packs into groups, for example:
The "stables" ones (the default)
The "incubating" ones.
...
We could start by defining this new "incubating" group but the solution should be open and should allow for extra groups. An option --feature-pack-discovery-groups=[grp1,grp2,...] would be open enough to implement the "incubating" group. For example: --feature-pack-discovery-group=incubating
Today all feature-packs WildFly Glow is discovering are put at the same level with respect to their maturity level. That is not reflecting the WildFly feature process in which some feature-packs could be incubating prior to reach the right stability level. WildFly Glow should separate these feature-packs into groups, for example:
We could start by defining this new "incubating" group but the solution should be open and should allow for extra groups. An option
--feature-pack-discovery-groups=[grp1,grp2,...]would be open enough to implement the "incubating" group. For example:--feature-pack-discovery-group=incubatingImplementation wise, the discovery-group name would be a branch in the https://github.com/wildfly/wildfly-galleon-feature-packs repository.
A user should be able to list the existing groups when calling the existing command:
show-configuration