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

Kevin Risden edited comment on SOLR-15990 at 2/10/22, 2:21 PM:
---------------------------------------------------------------

It looks like this is blocked by SOLR-15942 since the google-cloud-bom updates 
the Guava version.

The HDFS module tests get the following error:

{code:java}
org.apache.solr.core.HdfsDirectoryFactoryTest > classMethod FAILED
    java.lang.NoSuchMethodError: 'void 
com.google.common.util.concurrent.Futures.addCallback(com.google.common.util.concurrent.ListenableFuture,
 com.google.common.util.concurrent.FutureCallback)'
{code}



was (Author: risdenk):
It looks like this is blocked by SOLR-15942 since the google-cloud-bom updates 
the Guava version.

> Use google-cloud-bom for gcs-repository dependencies
> ----------------------------------------------------
>
>                 Key: SOLR-15990
>                 URL: https://issues.apache.org/jira/browse/SOLR-15990
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Build, contrib - GCS Repository
>            Reporter: Kevin Risden
>            Assignee: Kevin Risden
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently the gcs-repository module has most dependencies as 
> "transitive=false". This can be simplified to only pull in the dependencies 
> that are referenced at compile time and ensure Gradle pulls in the right 
> transitive dependencies. This makes it much easier to upgrade the google 
> clients without needing to find all the transitive dependency upgrades. As a 
> side effect, this removes a lot of the versions.prop lines that we don't need 
> to keep track of anymore.



--
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