Allow build to succeed even with stray sentry.properties file #4423
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the file is present in the `src/` directory (as when switching from an older branch), gradle will show this warning but otherwise succeed and use the correct updated version of the file: > Encountered duplicate path "sentry.properties" during copy operation configured with DuplicatesStrategy.WARN
cwisniew
approved these changes
Nov 18, 2023
kwvanderlinde
deleted the
refactor/4399-make-build-resilient-in-presence-of-stray-sentry-config
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Identify the Bug or Feature request
Improves PR #4401 for #4399
Description of the Change
When evaluating older commits, the lingering
sentry.propertiesfile makes the build fail due to conflicts with the new directly written version. This makes testing and bisecting more tedious than it needs to be. This PR introduces a change to allow the file to exist, but to ultimately have no effect other than this warning being generated:Possible Drawbacks
None
Documentation Notes
N/A
Release Notes
N/A
This change is