root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions 10 Packages Projects Releases Wiki Activity
rabbitmq-server/deps/rabbitmq_web_mqtt/app.bzl

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

169 lines
5.3 KiB
Python
Raw Permalink Normal View History

Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
load("@rules_erlang//:erlang_bytecode2.bzl", "erlang_bytecode")
load("@rules_erlang//:filegroup.bzl", "filegroup")
def all_beam_files(name = "all_beam_files"):
filegroup(
name = "beam_files",
srcs = [":other_beam"],
)
erlang_bytecode(
name = "other_beam",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
srcs = [
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
"src/Elixir.RabbitMQ.CLI.Ctl.Commands.ListWebMqttConnectionsCommand.erl",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
"src/rabbit_web_mqtt_app.erl",
"src/rabbit_web_mqtt_handler.erl",
"src/rabbit_web_mqtt_stream_handler.erl",
],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
hdrs = [":public_and_private_hdrs"],
app_name = "rabbitmq_web_mqtt",
dest = "ebin",
erlc_opts = "//:erlc_opts",
deps = [
"//deps/rabbit_common:erlang_app",
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
"//deps/rabbitmq_cli:erlang_app",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
"//deps/rabbitmq_mqtt:erlang_app",
"@cowboy//:erlang_app",
],
)
def all_test_beam_files(name = "all_test_beam_files"):
filegroup(
name = "test_beam_files",
testonly = True,
srcs = [":test_other_beam"],
)
erlang_bytecode(
name = "test_other_beam",
testonly = True,
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
srcs = [
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
"src/Elixir.RabbitMQ.CLI.Ctl.Commands.ListWebMqttConnectionsCommand.erl",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
"src/rabbit_web_mqtt_app.erl",
"src/rabbit_web_mqtt_handler.erl",
"src/rabbit_web_mqtt_stream_handler.erl",
],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
hdrs = [":public_and_private_hdrs"],
app_name = "rabbitmq_web_mqtt",
dest = "test",
erlc_opts = "//:test_erlc_opts",
deps = [
"//deps/rabbit_common:erlang_app",
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
"//deps/rabbitmq_cli:erlang_app",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
"//deps/rabbitmq_mqtt:erlang_app",
"@cowboy//:erlang_app",
],
)
def all_srcs(name = "all_srcs"):
filegroup(
name = "all_srcs",
srcs = [":public_and_private_hdrs", ":srcs"],
)
filegroup(
name = "public_and_private_hdrs",
srcs = [":private_hdrs", ":public_hdrs"],
)
filegroup(
name = "priv",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
srcs = ["priv/schema/rabbitmq_web_mqtt.schema"],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
)
filegroup(
name = "public_hdrs",
)
filegroup(
name = "srcs",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
srcs = [
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
"src/Elixir.RabbitMQ.CLI.Ctl.Commands.ListWebMqttConnectionsCommand.erl",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
"src/rabbit_web_mqtt_app.erl",
"src/rabbit_web_mqtt_handler.erl",
"src/rabbit_web_mqtt_stream_handler.erl",
],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
)
filegroup(
name = "private_hdrs",
)
filegroup(
name = "license_files",
Replace globs in bazel with explicit lists of files As this is preferred in rules_erlang 3.9.14
2023-04-25 23:09:24 +08:00
srcs = [
"LICENSE",
"LICENSE-MPL-RabbitMQ",
],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
)
def test_suite_beam_files(name = "test_suite_beam_files"):
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "test_src_rabbit_ws_test_util_beam",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/src/rabbit_ws_test_util.erl"],
outs = ["test/src/rabbit_ws_test_util.beam"],
Restore the original -include_lib statements from before #6466 since this broke erlang_ls requires rules_erlang 3.9.13
2023-04-20 18:36:08 +08:00
app_name = "rabbitmq_web_mqtt",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlc_opts = "//:test_erlc_opts",
)
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "test_src_rfc6455_client_beam",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/src/rfc6455_client.erl"],
outs = ["test/src/rfc6455_client.beam"],
Restore the original -include_lib statements from before #6466 since this broke erlang_ls requires rules_erlang 3.9.13
2023-04-20 18:36:08 +08:00
app_name = "rabbitmq_web_mqtt",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlc_opts = "//:test_erlc_opts",
)
bazel run gazelle
2024-10-01 22:14:29 +08:00
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "test_rabbit_web_mqtt_test_util_beam",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/rabbit_web_mqtt_test_util.erl"],
outs = ["test/rabbit_web_mqtt_test_util.beam"],
Restore the original -include_lib statements from before #6466 since this broke erlang_ls requires rules_erlang 3.9.13
2023-04-20 18:36:08 +08:00
app_name = "rabbitmq_web_mqtt",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlc_opts = "//:test_erlc_opts",
)
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "web_mqtt_command_SUITE_beam_files",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/web_mqtt_command_SUITE.erl"],
outs = ["test/web_mqtt_command_SUITE.beam"],
Restore the original -include_lib statements from before #6466 since this broke erlang_ls requires rules_erlang 3.9.13
2023-04-20 18:36:08 +08:00
app_name = "rabbitmq_web_mqtt",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlc_opts = "//:test_erlc_opts",
bazel run gazelle
2024-10-01 22:14:29 +08:00
deps = ["//deps/amqp_client:erlang_app", "//deps/rabbitmq_mqtt:erlang_app"],
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
)
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "web_mqtt_config_schema_SUITE_beam_files",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/web_mqtt_config_schema_SUITE.erl"],
outs = ["test/web_mqtt_config_schema_SUITE.beam"],
Restore the original -include_lib statements from before #6466 since this broke erlang_ls requires rules_erlang 3.9.13
2023-04-20 18:36:08 +08:00
app_name = "rabbitmq_web_mqtt",
Use gazelle generated bazel files Bazel build files are now maintained primarily with `bazel run gazelle`. This will analyze and merge changes into the build files as necessitated by certain code changes (e.g. the introduction of new modules). In some cases there hints to gazelle in the build files, such as `# gazelle:erlang...` or `# keep` comments. xref checks on plugins that depend on the cli are a good example.
2023-02-23 21:47:41 +08:00
erlc_opts = "//:test_erlc_opts",
)
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "web_mqtt_proxy_protocol_SUITE_beam_files",
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/web_mqtt_proxy_protocol_SUITE.erl"],
outs = ["test/web_mqtt_proxy_protocol_SUITE.beam"],
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
app_name = "rabbitmq_web_mqtt",
erlc_opts = "//:test_erlc_opts",
)
erlang_bytecode(
bazel run gazelle
2024-10-01 22:14:29 +08:00
name = "web_mqtt_shared_SUITE_beam_files",
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
testonly = True,
bazel run gazelle
2024-10-01 22:14:29 +08:00
srcs = ["test/web_mqtt_shared_SUITE.erl"],
outs = ["test/web_mqtt_shared_SUITE.beam"],
app_name = "rabbitmq_web_mqtt",
erlc_opts = "//:test_erlc_opts",
)
erlang_bytecode(
name = "web_mqtt_system_SUITE_beam_files",
testonly = True,
srcs = ["test/web_mqtt_system_SUITE.erl"],
outs = ["test/web_mqtt_system_SUITE.beam"],
app_name = "rabbitmq_web_mqtt",
erlc_opts = "//:test_erlc_opts",
)
erlang_bytecode(
name = "web_mqtt_v5_SUITE_beam_files",
testonly = True,
srcs = ["test/web_mqtt_v5_SUITE.erl"],
outs = ["test/web_mqtt_v5_SUITE.beam"],
bazel run gazelle for #10693
2024-03-17 01:38:11 +08:00
app_name = "rabbitmq_web_mqtt",
erlc_opts = "//:test_erlc_opts",
)