This repository has been archived by the owner on Dec 17, 2023. It is now read-only.
Make the plugin applicable to Settings instances #27
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.
The goal of this PR is to make the plugin applicable to Settings instances. The use case that gave me incentive to make this PR includes usage of credentials for custom repositories inside
pluginManagement
block ofsettings.gradle
.As the
Settings
class becameExtensionAware
only in Gradle 5.0, I was forced to use Gradle 5 here which broke compatibility of the plugin with Gradle pre-4.6 asorg.gradle.api.internal.tasks.options.Option
was removed in Gradle 5 whileorg.gradle.api.tasks.options.Option
was introduced only in Gradle 4.6. I think I can implement a workaround to restore compatibility with older versions if needed.