Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README.md lacks basic usage and clarity about built-in java support vs. what's provided by rules_java #80

Open
reddaly opened this issue Dec 19, 2022 · 1 comment
Labels
P2 We'll consider to work on this in future. (Assignee optional)

Comments

@reddaly
Copy link

reddaly commented Dec 19, 2022

I'm not clear on how users are supposed to use rules_java vs. the java rules that seem to come built into Bazel. The README.md could clarify this.

The special treatment is mentioned here, but I don't follow what's going on exactly bazelbuild/bazel#14370:

rules_java is still an external repository and it is imported by default via workspace prefix mechanism. The version of rules_java that is imported has not changed since 2019-07-03.

There is a "builtin" java_library implementation. But this does not change how rules_java are imported. So if you are loading a different version of rules_java in your WORKSPACE you should continue to do so.

What is the "workspace prefix mechanism?" How can I update or see what verison of rules_java are being imported implicitly? Why are such rules available using @bazel_tools rather than @rules_java?

@reddaly
Copy link
Author

reddaly commented Dec 20, 2022

Related to bazelbuild/bazel#4301

@hvadehra hvadehra added the P2 We'll consider to work on this in future. (Assignee optional) label Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider to work on this in future. (Assignee optional)
Projects
None yet
Development

No branches or pull requests

2 participants