We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 Eye (apache/skywalking-eyes)
Only a few selected text licenses are provided under assets/headers-templates
This causes the following issue:
WARNING failed to find a license template for spdx id EPL-2.0, open header-templates/EPL-2.0.txt: file does not exist
As EPL-2.0 ( and others ) are qualified SPDX ID licenses, is expected that would be found
Execute a check with this config:
header: license: spdx-id: EPL-2.0 copyright-owner: SW360 Frontend Authors copyright-year: '2023' software-name: sw360-frontend
An alternative solution would be the possibility to provide the License file in commandline or download in real time from SPDX.org
The text was updated successfully, but these errors were encountered:
I think the component should be skywalking-eyes. @heliocastro Please update the content.
Sorry, something went wrong.
Many thanks for so quick update
kezhenxu94
Successfully merging a pull request may close this issue.
Search before asking
Apache SkyWalking-Eyes Component
License Eye (apache/skywalking-eyes)
What happened
Only a few selected text licenses are provided under assets/headers-templates
This causes the following issue:
WARNING failed to find a license template for spdx id EPL-2.0, open header-templates/EPL-2.0.txt: file does not exist
What you expected to happen
As EPL-2.0 ( and others ) are qualified SPDX ID licenses, is expected that would be found
How to reproduce
Execute a check with this config:
Anything else
An alternative solution would be the possibility to provide the License file in commandline or download in real time from SPDX.org
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: