Fail if multiple transformation rules or bundles match the same license
Vampire opened this issue · 1 comments
Vampire commented
If you have org.hamcrest:hamcrest
in your dependencies and use the LicenseBundleNormalizer
with default rules, Hamcrest is reported as having both, 0BSD and BSD-3-Clause.
This is because for each a transformation rule matches. In this case even for different properties. There is an URL pattern that correctly matches the BSD-3-Clause URL, and then the name pattern BSD( |-)license.*
which matches the name "BSD License 3" as 0BSD.
I needed quite some time to realize where this 0BSD is coming from.
Vampire commented
Hm, I guess this will not really work out, as there could really be multiple licenses mentioned that should be taken into account, but the rules need to be changed.