Currently acs-aem-commons-all package mixes subpackages with configuration files. This change bundles the configurations in a separate package which is also included in the all package.
Another benefit is that it allows other projects to include individual ACS Commons packages while not missing the OSGI configurations (e.g. include the acs-aem-commons-bundle and acs-aem-commons-ui.config only).
Also, by including individual packages separately it's possible to control the packages installation order. This is currently impossible since including the acs-aem-commons-all is the only way to install OSGI Configurations.
Corresponding issue: https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/3433
Currently acs-aem-commons-all package mixes subpackages with configuration files. This change bundles the configurations in a separate package which is also included in the all package.
Another benefit is that it allows other projects to include individual ACS Commons packages while not missing the OSGI configurations (e.g. include the acs-aem-commons-bundle and acs-aem-commons-ui.config only).
Also, by including individual packages separately it's possible to control the packages installation order. This is currently impossible since including the acs-aem-commons-all is the only way to install OSGI Configurations.