rabbitmq-server/bazel/elixir/BUILD.bazel

load(
    ":elixir_as_app.bzl",
    "elixir_as_app",
)

toolchain_type(
    name = "toolchain_type",
    visibility = ["//visibility:public"],
)

elixir_as_app(
    name = "erlang_app",
    visibility = ["//visibility:public"],
)

elixir_as_app(
    name = "logger",
    app = "logger",
    visibility = ["//visibility:public"],
)

elixir_as_app(
    name = "iex",
    app = "iex",
    visibility = ["//visibility:public"],
)
Make rabbitmq-server work with rules_erlang 3 Also rework elixir dependency handling, so we no longer rely on mix to fetch the rabbitmq_cli deps Also: - Specify ra version with a commit rather than a branch - Fixup compilation options for erlang 23 - Add missing ra reference in MODULE.bazel - Add missing flag in oci.yaml - Reduce bazel rbe jobs to try to save memory - Use bazel built erlang for erlang git master tests - Use the same cache for all the workflows but windows - Avoid using `mix local.hex --force` in elixir rules - Fetching seems blocked in CI, and this should reduce hex api usage in all builds, which is always nice - Remove xref and dialyze tags since rules_erlang 3 includes them in the defaults 2022-05-17 20:07:16 +08:00			`load(`
			`":elixir_as_app.bzl",`
			`"elixir_as_app",`
			`)`

			`toolchain_type(`
			`name = "toolchain_type",`
			`visibility = ["//visibility:public"],`
			`)`

			`elixir_as_app(`
			`name = "erlang_app",`
			`visibility = ["//visibility:public"],`
			`)`
Account for Elixir containing several core applications - eex - elixir - ex_unit - iex - logger - mix So that apps (like rabbitmq_cli) can dialyze against the extra components 2023-05-04 18:52:08 +08:00
			`elixir_as_app(`
			`name = "logger",`
			`app = "logger",`
			`visibility = ["//visibility:public"],`
			`)`

			`elixir_as_app(`
			`name = "iex",`
			`app = "iex",`
			`visibility = ["//visibility:public"],`
			`)`