-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
dependency_data files do not need licenses #3772
dependency_data files do not need licenses #3772
Conversation
...on the basis that they only contain version strings, jar names, and SHAs that are obtained from external sources. Signed-off-by: Adam Farley <adfarley@redhat.com>
Do you need to remove some incorrectly added too? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A block has been put on this Pull Request as this repository is temporarily under a code freeze due to an ongoing release cycle.
If this pull request needs to be merged during the release cycle then please comment /merge
and a PMC member will be able to remove the block.
If the code freeze is over you can remove this block by commenting /thaw
.
Block was incorrectly applied to PR for master branch.
@adamfarley Feel free to merge once you've addressed Tim's Q. |
I don't think so, no. I'm adding just one entry, and it exclusively covers a directory that contains sha256 files and version string files. I did review the rest of the list. Maybe you're suggesting that getDependencies should have a license at the top of that groovy file, and its entry be excluded here? I didn't think it did, as other groovy files in our repos don't have licenses (example). |
Thanks @gdams |
...on the basis that they only contain version strings, jar names, and SHAs that are obtained from external sources.