Kudos to Michal Petrov for the work he's been doing around license reporting, and FYI to you all about it.
Apologies in advance if I get some of this wrong, but the gist of it is Michal embedded the canonical information about how to describe licenses within our licenses plugin itself.[1] This is the plugin we use to generate the licenses.xml and licenses.html content users finds in docs/licenses in a WildFly installation.
I believe the effect of this is if a dev adds a new artifact to a feature pack it is no longer required to add license data to our feature pack source unless the artifact's associated pom doesn't have correct license data. If you do need to add license info for the artifact, it's only necessary to state the name of the license (one of the names listed in [1].)
If the "KnownLicenses" class in the plugin[1] doesn't have information about a license, it's possible in the feature pack source to declare that information and then reference it. See [2] as an example from the plugin testsuite.
Thanks, Michal! This is a nice improvement that largely eliminates an unintuitive boilerplate step when integrating new functionality.
Brian