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

Add rules_java 4.0.0 #17

Merged
merged 1 commit into from
Oct 20, 2021
Merged

Conversation

meteorcloudy
Copy link
Member

Context: #7

compatibility_level = 1,
)
bazel_dep(name = "bazel_skylib", version = "1.0.3")

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just curious, what's our policy for adding the MODULE.bazel file itself as a patch? I see you have done it for some other modules (rules_python for example), but not done it here. It probably doesn't matter too much either way; I just thought we should be consistent.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, for other modules, it's because I have other changes to patch so the patch for MODULE.bazel was generated together, I should have just removed it since it's not necessary. But ideally both MODULE.bazel and those changes should be upstreamed.

@meteorcloudy meteorcloudy merged commit f6af4d0 into bazelbuild:main Oct 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants