aboutsummaryrefslogtreecommitdiff
path: root/examples/my_org/compliance/BUILD
diff options
context:
space:
mode:
authorBill Neubauer <wcn@google.com>2022-10-24 19:52:53 -0400
committerTony Aiuto <aiuto@google.com>2022-11-01 00:32:59 -0400
commitd8c455ebb46b0f489a4a83367e4833fda5a131db (patch)
tree15432eb15d61d926fadba52d89209698ea4bd324 /examples/my_org/compliance/BUILD
parent84c8fe9fabbd149dff42f854c07fabbe286f93a8 (diff)
downloadbazelbuild-rules_license-d8c455ebb46b0f489a4a83367e4833fda5a131db.tar.gz
Mega merge from Google
The core of the PR is an expert from Google, but it applies several changes to account for Bazel differences. - deal with bazel 5.x 6.x @// handling - restore package_url and package_version. This is temporary they will move to other providers. PiperOrigin-RevId: 483521567
Diffstat (limited to 'examples/my_org/compliance/BUILD')
-rw-r--r--examples/my_org/compliance/BUILD31
1 files changed, 0 insertions, 31 deletions
diff --git a/examples/my_org/compliance/BUILD b/examples/my_org/compliance/BUILD
deleted file mode 100644
index 074b21e..0000000
--- a/examples/my_org/compliance/BUILD
+++ /dev/null
@@ -1,31 +0,0 @@
-# Example license policy definitions.
-
-load("@rules_license//rules:license_policy.bzl", "license_policy")
-
-package(default_visibility = ["//examples:__subpackages__"])
-
-# license_policy rules generally appear in a central location per workspace. They
-# are intermingled with normal target build rules
-license_policy(
- name = "production_service",
- conditions = [
- "notice",
- "restricted_if_statically_linked",
- ],
-)
-
-license_policy(
- name = "mobile_application",
- conditions = [
- "notice",
- ],
-)
-
-license_policy(
- name = "special_whitelisted_app",
- # There could be a whitelist of targets here.
- conditions = [
- "notice",
- "whitelist:acme_corp_paid",
- ],
-)