[jira] [Commented] (LUCENE-10138) Use maven central for gradle plugin repository

["Dawid Weiss (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-10138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422641#comment-17422641 ] 

Dawid Weiss commented on LUCENE-10138:
--------------------------------------

jcenter is deprecated and should be removed from the build entirely, actually...

> 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
>            Priority: Major
>
> 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.
>  
> {{ pluginManagement {}}
> {{  repositories {}}
> {{    mavenCentral()}}
> {{    gradlePluginPortal()}}
> {{  }}}
> {{ }}}
>  
> cc [~dweiss]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org