[GRADLE-3502] Plugin portal does not provide transitive dependencies for plugins from custom repositories Created: 14/Jul/16 Updated: 15/Jul/16 Resolved: 15/Jul/16 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 2.14 |
| Fix Version/s: | 3.0-rc-1 |
| Type: | Bug | ||
| Reporter: | Stefan Oehme (Inactive) | Assignee: | Stefan Oehme (Inactive) |
| Resolution: | Fixed | Votes: | 1 |
| Description |
|
Given these plugin repositories:
pluginRepositories {
maven {
url 'my-company-repo'
}
gradlePluginPortal()
}
When a plugin from the company-repo depends on another plugin from the plugin portal, it cannot be resolved. The workaround is to explicitly add the plugin portal maven repository as another plugin repository:
pluginRepositories {
maven {
url 'my-company-repo'
}
gradlePluginPortal()
maven {
url 'https://plugins.gradle.org/m2'
}
}
|