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
Make it possible to disable rewriting log4j.properties #220
Make it possible to disable rewriting log4j.properties #220
Changes from all commits
1269a61
a151710
ce2a8c5
3bf3462
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.
SInce I'm unfamiliar with the SDK, I am probably missing something, but won't this change result in always throwing when on version < 6.2, while the intention is to only warn when you want to disable the task?
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.
What we do here is setting the
outputWar
property tonull
when this task is disabled.This signals to the tasks that consume the output war (so
createDockerFile
&alfrescoWar
) that there is no file to add.We do not want to warn when disabling the task on < 6.2, we want to actively fail the build with a clear error message.
Returning
null
from amap()
results in a vague exception in Gradle versions before 6.2. Thex ? y : z
operator is equivalent toif(x) { return y; } else { return z; }
, the non-matching side will not be evaluated at all.On the other hand, keeping the output file when the task is disabled will result in an exception from the tasks that consume the output war, because the promised output file does not actually exists (not generated, because the task is not run).
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.
Thank you for the thorough explanation.