The license files are used to overwrite the license information of the artifacts available as maven dependencies.

These configuration license files are using ${project.groupId} and other maven variables that in some cases are not being replaced by the current environment values. Consequently, the maven license plugin is unable to match the artifact with the configuration supplied on the license file.

I've found this issue with the wildfly-preview feature pack, however, other feature packs could be affected.