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

Mike Drob commented on SOLR-15915:
----------------------------------

the version of the gradle plugin that we use still depends on an old grolifant 
plugin, which was on bintray 
https://github.com/apache/solr/runs/4794885328?check_suite_focus=true

it looks like current plugin development uses a newer version 
https://github.com/jruby-gradle/jruby-gradle-plugin/blob/master/gradle.properties#L17
and that version is on maven central 
https://search.maven.org/artifact/org.ysb33r.gradle/grolifant60/1.0.0-alpha.6/jar

but there's no released version of the jruby plugin that uses that? the 
versions available on https://github.com/jruby-gradle/jruby-gradle-plugin don't 
match the tags in https://github.com/jruby-gradle/jruby-gradle-plugin so it's 
hard to tell.

> Move ref guide away from using jcenter repo
> -------------------------------------------
>
>                 Key: SOLR-15915
>                 URL: https://issues.apache.org/jira/browse/SOLR-15915
>             Project: Solr
>          Issue Type: Task
>            Reporter: Mike Drob
>            Priority: Blocker
>
> The JCenter repo is long gone and we need to update our plugin resolution. 
> The gradle-jruby website still points people at JCenter, but the plugin looks 
> like is getting published to the gradle plugin portal as well, so it should 
> be safe to move.
> https://plugins.gradle.org/plugin/com.github.jruby-gradle.base
> This is causing precommit checks to fail on GitHub, and probably anything 
> else building the ref guide.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to