You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2020. It is now read-only.
Using a single Maven plugin repository will be sufficient for many users. It is thus a great first step for wiring up the repository declaration with the resolver.
Proposed Change
Replace the org.gradle.plugin.repoUrl system property with the URL of the single Maven repository defined in the pluginRepositories block.
Introduce DefaultPluginRepositoryHandler, MavenPluginRepository (this overlaps with #17) and PluginRepositoryInternal. These will form the back-end for the DSL introduced by #17.
The resolvers derived from these repositories are added before the Plugin Portal resolver. This replaces the single "CustomRepositoryResolver". The name mentioned in resolution failure messages should equal the name that the user set on the plugin repository.
Motivation
Using a single Maven plugin repository will be sufficient for many users. It is thus a great first step for wiring up the repository declaration with the resolver.
Proposed Change
Replace the
org.gradle.plugin.repoUrl
system property with the URL of the single Maven repository defined in thepluginRepositories
block.Introduce
DefaultPluginRepositoryHandler
,MavenPluginRepository
(this overlaps with #17) andPluginRepositoryInternal
. These will form the back-end for the DSL introduced by #17.The resolvers derived from these repositories are added before the Plugin Portal resolver. This replaces the single "CustomRepositoryResolver". The name mentioned in resolution failure messages should equal the name that the user set on the plugin repository.
Test cases
Code Review
The text was updated successfully, but these errors were encountered: