-
Notifications
You must be signed in to change notification settings - Fork 213
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
Remove legacy Javac compilation #694
Remove legacy Javac compilation #694
Conversation
bb7833a
to
1dab3a1
Compare
14c2982
to
ae2b517
Compare
…es/jetpack_compose/BUILD
@@ -90,13 +88,6 @@ class KotlinJvmTaskExecutor @Inject internal constructor( | |||
emptyList() | |||
} | |||
} | |||
context.execute("javac") { |
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.
It looks to me that we were compiling java twice, once here and once in https://sourcegraph.com/github.com/bazelbuild/rules_kotlin/-/blob/kotlin/internal/jvm/compile.bzl?L699
I'm still testing this against our code base but so far it seems like it's safe to remove this -- didn't notice huge perf gains but we dont have that much java in our codebase
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.
This works with our repo. I think it's safe to submit this and close #678 as it will no longer be relevant.
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'll need to cut 1.6 alpha candidate to get more testing.
@restingbull sounds good. I'm going to merge this one in and we can look into the java_home/rbe issues async d0abebe |
To repro, run `./run.sh` Before bazelbuild/rules_kotlin#694 this succeeded, now it fails.
To repro, run `./run.sh` Before bazelbuild/rules_kotlin#694 this succeeded, now it fails.
Notable changes: