License Scanning reports no license for some complex Gradle projects
This has been closed in favor of 4 additional issues
- License Scanning doesn't handle dependencies defined using implementation directive: #341222 (closed)
- License Scanning doesn't handle dependency constraints: #341468 (closed)
- License Scanning doesn't handle subprojects: #341470
- License Scanning encounters "GC overhead limit exceeded" error for large gradle configurations with subprojects: #341500 (closed)
It appears that 1.
is completely distinct, while 2.
and 3.
are closely related, and a solution to 3.
might also solve 2.
, but this needs further investigation.
Summary
An Ultimate customer reports (internal ticket) that our License Scanner works fine for projects that follow the structure of this example, but not for other examples.
For some complex multi-project Gradle builds, license-finder reports no licenses at all, and it does not even fail. This is misleading, and users might think the scan was successful.
At this point we don't know what makes license-finder silently fail.
Steps to reproduce
Example Project
What is the current bug behavior?
What is the expected correct behavior?
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true
)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
)(we will only investigate if the tests are passing)