Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License is not compatible with ORT tool #266

Open
yegor256 opened this issue Jan 15, 2025 · 2 comments
Open

License is not compatible with ORT tool #266

yegor256 opened this issue Jan 15, 2025 · 2 comments

Comments

@yegor256
Copy link

yegor256 commented Jan 15, 2025

When I'm scanning my project using ORT toolkit, it complains:

WARNING: UNMAPPED_DECLARED_LICENSE - Maven:edu.berkeley.cs.jqf:jqf-instrument:2.0 - The declared license 'FreeBSD License' could not be mapped to a valid license or parsed as an SPDX expression. The license was found in package 'Maven:edu.berkeley.cs.jqf:jqf-instrument:2.0'.
WARNING: UNMAPPED_DECLARED_LICENSE - Maven:edu.berkeley.cs.jqf:jqf-fuzz:2.0 - The declared license 'FreeBSD License' could not be mapped to a valid license or parsed as an SPDX expression. The license was found in package 'Maven:edu.berkeley.cs.jqf:jqf-fuzz:2.0'.
ERROR: NO_LICENSE_IN_DEPENDENCY - Maven:edu.berkeley.cs.jqf:jqf-instrument:2.0 - No license information is available for dependency 'Maven:edu.berkeley.cs.jqf:jqf-instrument:2.0'.
ERROR: NO_LICENSE_IN_DEPENDENCY - Maven:edu.berkeley.cs.jqf:jqf-fuzz:2.0 - No license information is available for dependency 'Maven:edu.berkeley.cs.jqf:jqf-fuzz:2.0'.

Maybe in JQF we can replace FreeBSD License text in the pom.xml with something SPDX compatible, see https://spdx.github.io/spdx-spec/v2-draft/SPDX-license-expressions/

@sschuberth
Copy link

More specifically, you should generally use an SPDX license identifier from this list.

@rohanpadhye
Copy link
Owner

Thanks, I realize the naming was sloppy earlier (and funnily nobody ever complained before, even though I know of several big-tech orgs using JQF internally). The fix is in #267 is good. I also need to do a more general pass to ensure consistency of copyright holder names, etc. which I'll do before making a 2.1 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants