[bazel.build] Problem with /basics/dependencies
- Dominant language
- Java
- Stars
- 25.8k
- Forks
- 4.6k
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 72
Description
### Page link:
https://bazel.build/basics/dependencies
### Problem description (include actual vs expected text, if applicable):
> Projects that use artifact-based build systems like Bazel are broken into a set
of modules, with modules expressing dependencies on one another via `BUILD`
files.
>
> In Bazel, a *module* is represented by a target specifying a buildable unit like a
`java_library` or a `go_binary`
>
Throughout this article there are references to "Bazel module" but there is the possibility of confusion with https://bazel.build/reference/glossary#module , which is an unrelated concept.
What is the distinction between "module" (as used in the quotes above) and "target"?
### Where do you see this issue? (include link to specific section of the page, if applicable)
https://bazel.build/basics/dependencies
### Any other information you'd like to share?
_No response_
Contributor guide
Research direction
Open the linked /basics/dependencies page and review the quoted paragraphs alongside the Bazel glossary entry for “module.” Clarify the terminology on that page so readers can distinguish the article’s use of “module” from the glossary concept and understand its relationship to a target; the page should no longer leave those terms confusingly conflated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- build-system
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100