Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Deprecate jib.extraDirectory in Gradle #1671
Deprecate jib.extraDirectory in Gradle #1671
Changes from 11 commits
474ef7c
fbbe7d3
85817ef
b92289f
b4654fd
853fd80
37145c8
2c43f12
342f1ea
4d47bc4
45a8a39
f5f5c82
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm curious how necessary this is, would prefer we didn't need to keep track of things with flags?
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.
Yeah, this is quite unfortunate. The Gradle case wasn't easy for a few reasons.
JibExtension
orExtraDirectoriesParameters
.extraDirectories.paths
orextraDirectory.path
in our codebase for consumption is to first go throughgetExtraDirectories()
, which is also used by Gradle to set in config values, so unlike Maven, it's not possible to check if the user is using the old or new syntax (or both) insidegetExtraDirectories()
. On top of that, Gradle always calls bothgetExtraDirectory()
andgetExtraDirectories()
regardless of whether the user has ever configured anything.So, although this is very unfortunate, I couldn't find a good alternative.