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

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

2.1.0-alpha.1 still depends on a too old version of grolifant that sonly in 
jcenter.

2.1.0-alpha.2 which may not be a real version because there is no tag in the 
plugin repo fails with:
{noformat}
> Task :solr:solr-ref-guide:jrubyPrepare FAILED

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task 
':solr:solr-ref-guide:jrubyPrepare' (type 'JRubyPrepare').
  - In plugin 'com.github.jruby-gradle.base' type 
'com.github.jrubygradle.JRubyPrepare' property 'projectOperations' is missing 
an input or output annotation.

    Reason: A property without annotation isn't considered during up-to-date 
checking.

    Possible solutions:
      1. Add an input or output annotation.
      2. Mark it as @Internal.

    Please refer to 
https://docs.gradle.org/7.2/userguide/validation_problems.html#missing_annotation
 for more details about this problem.
{noformat}

> 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