-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
rsc doesn't re-snapshot jars produced by zinc #7858
rsc doesn't re-snapshot jars produced by zinc #7858
Conversation
Instead it re-uses existing digests from the classpath product. A follow-up change will also stop re-snapshotting jars produced by rsc.
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.
Thanks!
main = 'rsc.cli.Main' | ||
tool_name = 'rsc' | ||
with self.context.new_workunit(tool_name) as wu: | ||
return self.execution_strategy_enum.resolve_for_enum_variant({ | ||
self.HERMETIC: lambda: self._runtool_hermetic( | ||
main, tool_name, args, distribution, | ||
tgt=tgt, input_files=input_files, input_digest=input_digest, output_dir=output_dir), | ||
tgt=tgt, input_digest=input_digest, output_dir=output_dir), |
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.
👍
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.
Great!
I pushed one commit to drop an unused import. |
Instead it re-uses existing digests from the classpath product. A follow-up change will also stop re-snapshotting jars produced by rsc.
Instead it re-uses existing digests from the classpath product.
A follow-up change will also stop re-snapshotting jars produced by rsc.