Remove explicit ProGuard plugin dependencies #2041
Merged
Conversation
This file contains hidden or 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
Explicitly specifying dependencies only seems to be necessary when using `<proguardVersion>` config element to override version (and even that might not be necessary; only adding explicit dependencies might suffice). However, when omitting it, plugin uses a recent ProGuard version on its own.
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.
Explicitly specifying dependencies only seems to be necessary when using
<proguardVersion>config element to override version (and even that might not be necessary; only adding explicit dependencies might suffice). However, when omitting it, plugin uses a recent ProGuard version on its own.So it was most likely redundant by me to include the explicit ProGuard dependencies and the
<proguardVersion>in #1964 in the first place, sorry.