rules_license
rules_license copied to clipboard
bazelbuild
Matches the rules authors SIG recommendations in https://github.com/bazel-contrib/rules-template Fixes #132
Allows package manager implementations like rules_jvm_external to begin declaring the licenses or other metadata about third-party packages they fetch and add to the dependency graph. Needs some discussion with @mzeren-vmw...
Remove the use of a deprecated API. > It's a good idea to open an issue first for discussion. - [x] Tests pass - [x] Tests and examples for any...
## Expected Behavior `gather_licenses_info.bzl` should also gather license from external packages (fetched thru `WORKSPACE` or `Bzlmod`). ## Actual Behavior `gather_licenses_info.bzl` only gathers license from in-tree project sources and vendored dependencies....
Typically, every BUILD file in a bazel module is under the license defined at `//:license`. Since Bazel does not have inheritance from enclosing packages, we must usually add: ``` package(default_package_metadata=["//:license",...
Hello, I have to list all the external dependencies of a bazel built project ([envoy](https://github.com/envoyproxy/envoy)), with their name, version and license(s). It seems `rules_license` would help me in this task,...
https://github.com/bazelbuild/bazel//commit/e54078fbe408a77a55cdaec7f0b8b35b19ae3010
I couldn't find any issue tracking this but please enlighten me if that is the case. Has there been any thoughts on creating a tool for gathering the license info...
