[
https://issues.apache.org/jira/browse/LUCENE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward resolved LUCENE-10138.
------------------------------------
Fix Version/s: main (9.0)
Assignee: Alan Woodward
Resolution: Fixed
> Use maven central for gradle plugin repository
> ----------------------------------------------
>
> Key: LUCENE-10138
> URL: https://issues.apache.org/jira/browse/LUCENE-10138
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Fix For: main (9.0)
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> By default, the gradle plugin repository downloads its plugins from jcenter.
> Jcenter can be a bit flaky when it comes to serving jar files, which is not
> normally a problem as gradle will generally only have to download its plugins
> once. But if you have a CI setup that starts each run completely fresh (as
> for example we do at elastic) then there's a high chance that any given CI
> run will fail due to jcenter download errors.
> Ideally we could fix this by having a local setup that overrides the standard
> configuration, but there doesn't seem to be a way to do this for plugin
> management.
> I'd like to add the following to our gradle config. This will make gradle
> look in maven central for third party plugins before looking at jcenter.
> {code}
> pluginManagement {
> repositories {
> mavenCentral()
> gradlePluginPortal()
> }
> }
> {code}
>
> cc [~dweiss]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
