Release 0.7.2
Bugfix release: fixes compatibility issues with Bazel 7.4 and 8.0.
Note that this release breaks compatibility with g++ 7.5 (the default compiler in the Ubuntu 18.04 image) - a new transitive dep requires a newer c++ compiler version.
Contributors
Alexandre Rostovtsev, Hemanshu Vadehra, Philip Zembrod, Richard Levasseur
MODULE.bazel setup
bazel_dep(name = "stardoc", version = "0.7.2")
By default - in other words, when using Bzlmod for dependency management - Stardoc uses @stardoc
as its repo name. The legacy WORSKSPACE
setup (see below) used @io_bazel_stardoc
instead. For compatibility with the legacy WORKSPACE
setup, you may add repo_name = "io_bazel_stardoc"
to the bazel_dep
call.
Legacy WORKSPACE setup
To use Stardoc, add the following to your WORKSPACE
file:
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "io_bazel_stardoc",
sha256 = "0e1ed4a98f26e718776bd64d053d02bb34d98572ccd03d6ba355112a1205706b",
urls = [
"https://mirror.bazel.build/github.com/bazelbuild/stardoc/releases/download/0.7.2/stardoc-0.7.2.tar.gz",
"https://github.com/bazelbuild/stardoc/releases/download/0.7.2/stardoc-0.7.2.tar.gz",
],
)
load("@io_bazel_stardoc//:setup.bzl", "stardoc_repositories")
stardoc_repositories()
load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")
rules_java_dependencies()
load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")
protobuf_deps()
load("@rules_jvm_external//:repositories.bzl", "rules_jvm_external_deps")
rules_jvm_external_deps()
load("@rules_jvm_external//:setup.bzl", "rules_jvm_external_setup")
rules_jvm_external_setup()
load("@io_bazel_stardoc//:deps.bzl", "stardoc_external_deps")
stardoc_external_deps()
load("@stardoc_maven//:defs.bzl", stardoc_pinned_maven_install = "pinned_maven_install")
stardoc_pinned_maven_install()
The sequence of function calls and load statements after the io_bazel_stardoc
repository definition ensures that this repository's dependencies are loaded (each function call defines additional repositories for Stardoc's dependencies, which are then used by subsequent load statements).
Note that WORKSPACE
files are sensitive to the order of dependencies. If, after updating to a newer version of Stardoc, you encounter "not a valid maven_install.json file" or other repository fetch errors (example: #186), try moving the Stardoc dependency block above or below other dependencies in your WORKSPACE
file.
Using the rules
See the source.