| commit | abe8c1d1bbbe874e594ce0fc41f16b1566f1891a | [log] [tgz] |
|---|---|---|
| author | Alexandre Rostovtsev <arostovtsev@google.com> | Fri Aug 04 15:24:30 2023 -0400 |
| committer | GitHub <noreply@github.com> | Fri Aug 04 15:24:30 2023 -0400 |
| tree | df29260016dad382f8e90466597de883dabceaae | |
| parent | 799f388ecdb790e6d7f6bf6eebaa2c0befb807fe [diff] |
List maven artifacts in MODULE.bazel to avoid rules_jvm_external pin warning (#176) Since we no longer have a single source of truth for maven artifacts, we need a consistency test. Use some old-school sed to extract the STARDOC_MAVEN_ARTIFACTS list from MODULE.bazel and deps.bzl, and add a test to ensure they are consistent. And - for good measure - add a similar test to ensure the version number in version.bzl and MODULE.bazel is consistent too. Fixes #174
Stardoc is a documentation generator for Bazel build rules written in Starlark.
Stardoc provides a Starlark rule (stardoc, see documentation) that can be used to build documentation for Starlark rules in Markdown. Stardoc generates one documentation page per .bzlfile.
Stardoc is a replacement for the deprecated “Skydoc” documentation generator.
See Skydoc Deprecation for details on the deprecation and migration details.
See our future plans for refactoring Stardoc to be more consistent with how Bazel evaluates .bzl files, and what it means for maintenance of this project.
See the maintaner's guide for instructions for cutting a new release.