GNU GPL2 with Class Path Exception reported as GNU GPL2
Summary
When using GitLab's License Management capability, the GNU General Public License, version 2 with the Classpath Exception license is detected by license_finder as GPL2 w/ CPE
and subsequently recorded within GitLab as GPL2
Steps to reproduce
You can see the pipeline that shows license_finder and it appropriately reporting the license.
https://gitlab.com/gitlab-gold/tpoffenbarger/secure-defend/jakarta-license/-/jobs/1718310679#L69
Example Project
https://gitlab.com/gitlab-gold/tpoffenbarger/secure-defend/jakarta-license
What is the current bug behavior?
The license identified by license_finder
(which is correct) is different than what GitLab reports.
What is the expected correct behavior?
GitLab should correctly identify the license as GNU GPL2 with Class Path Exception
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)
Implementation plan
- Change normilized licenses by unlinking
GPL2 w/ CPE
andGNU General Public License v2.0 only, with Classpath exception
fromGPL-2.0-only
toGPL-2.0-with-classpath-exception
- Update tests that fail with this change