Ensure all tests use loadable .bzl modules (#155)

In preparation for switching to starlark_doc_extract, we need to fix Stardoc tests to use .bzl files that can really be loaded by Bazel. This means:
* getting rid of misuses of aspect api
* getting rid of old Android and Java symbols
* getting rid of generated_bzl_test entirely, since Bazel cannot load dynamically generated .bzl modules.

Also fix update-stardoc-tests.sh script - we need to ignore the _stardoc java_binary outputs introduced by #141.
16 files changed
tree: a7f15d516bda792eecee8027abb32fb320b44c50
  1. .bazelci/
  2. distro/
  3. docs/
  4. stardoc/
  5. test/
  6. .bazelignore
  7. .bazelrc
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CHANGELOG.md
  12. CODEOWNERS
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. LICENSE
  16. maven_install.json
  17. MODULE.bazel
  18. README.md
  19. rules_jvm_external.patch
  20. setup.bzl
  21. update-release-binary.sh
  22. update-stardoc-docs.sh
  23. update-stardoc-tests.sh
  24. version.bzl
  25. WORKSPACE
README.md

Stardoc - Starlark Documentation Generator

Build status

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.

Get Started

About Stardoc

Project Status

Skydoc deprecation

Stardoc is a replacement for the deprecated “Skydoc” documentation generator.

See Skydoc Deprecation for details on the deprecation and migration details.

Future plans

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.

Maintainer's guide

See the maintaner's guide for instructions for cutting a new release.