-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
[Bazel] Use rules_jvm_external to manage java dependencies #4615
Conversation
Test PASSed. |
Test FAILed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's much cleaner. Please fix the lint error and resolve the conflicts.
@@ -17,7 +17,7 @@ java_binary( | |||
visibility = ["//visibility:public"], | |||
deps = [ | |||
":org_apache_arrow_arrow_plasma", | |||
"@junit_junit//jar", | |||
"@maven//:junit_junit", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We use TestNG instead of JUnit, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plasma still uses junit.
Test PASSed. |
Test PASSed. |
Test FAILed. |
Test FAILed. |
Test PASSed. |
Test FAILed. |
This PR contains changes that help with memory issues ray-project#4615
What do these changes do?
Unlike the current bazel-deps tool, rules_jvm_external doesn't need to check in the auto-generated
worksapce.bzl
file.Related issue number
Linter
scripts/format.sh
to lint the changes in this PR.