Carl Mai

I have a PR open: #297 which should fix the issue. I think it was not the problem, that the License came from a license file, but that the plugin...

@chadlwilson / @bdellegrazie / @jk1 what do you think about the PR? We use it in our project already for some time. If there is interest, I can rebase it.

Rebased and also added a commit: https://github.com/balrok/Gradle-License-Report/commit/0532295c64e080214519d2e6163df89ae6824e9f Reason it is needed: we have several plugins creating code for us. Also we want to better be safe than sorry

@chadlwilson / @bdellegrazie / @jk1 what do you think about the PR? It should not be a breaking change because the old behavior is preserved. But now the way how...

That a dependency has more than one license can happen for various reasons: * the dependency bundles other code together with their license (like @chadlwilson explained) This is effectively an...

I had a look at my list. Everything is done by hand. At least from my findings I see some false-positives. I also see cases where our license-normlization didn't catch...

I also want to give one more argument for this config-option: - We will always get false positives. A false-positive may hide an incompatible license from the check. - Without...

Sorry, I have the feeling this discussion is not really about the PR anymore. The main reason for this PR is make it configurable how licenses are checked. This is...