search

rholder / guava-retrying

This is a small extension to Google's Guava library to allow for the creation of configurable retrying strategies for an arbitrary function call, such as something that talks to a remote service with flaky uptime.
Apache License 2.0
1.43k stars 275 forks source link

Failed to collect dependencies at com.github.rholder:guava-retrying:jar:2.0.0 #104

Open nicodmt opened 2 years ago

nicodmt commented 2 years ago

Hi, we are experiencing issues using the dependency. This started between a few days ago to a couple of weeks (unsure because of vacation...).

The logs are telling us this:

Could not resolve dependencies for project XX.XXX.XXX: Failed to collect dependencies at com.github.rholder:guava-retrying:jar:2.0.0 -> com.google.guava:guava:jar:31.1.0.redhat-00001: Failed to read artifact descriptor for com.google.guava:guava:jar:31.1.0.redhat-00001: Could not find artifact com.google.guava:guava-parent:pom:31.1.0.redhat-00001 in central (https://repo1.maven.org/maven2)

I've already asked the team at Guava who are firmly saying the issue is not on their side and I now see that the issue is from here because we are using:

`

com.github.rholder 
        <artifactId>guava-retrying</artifactId>
        <version>2.0.0</version>
    </dependency>`

How can this be fixed?

javabrett commented 2 years ago

From db entry https://mvnrepository.com/artifact/com.google.guava/guava/31.1.0.redhat-00001 ...

It seems possible that this artifact was previously published under https://maven.repository.redhat.com/earlyaccess/all/ , but no longer is?

nicodmt commented 2 years ago

That is a possibility, I have unfortunately no answer on why the problem happened but I have a solution. We changed dependency to a fork from rholder guava-retrying which is updated and backed. I'll link it below:

    <!-- https://mvnrepository.com/artifact/io.github.itning/guava-retrying3 -->
    <dependency>
        <groupId>io.github.itning</groupId>
        <artifactId>guava-retrying3</artifactId>
        <version>3.0.1</version>
    </dependency>
ShakHussan commented 1 year ago

Is it possible that incorrect dependency can get updated back?

ShakHussan commented 1 year ago

I checked the pom files. Mostly issue is due to presence of image And there is a change in guava version naming.

mkrzywanski commented 1 year ago

You can just exclude the guava from this lib and pin to specific version that used to work before : 

<dependency>
            <groupId>com.github.rholder</groupId>
            <artifactId>guava-retrying</artifactId>
            <version>2.0.0</version>
            <exclusions>
                <exclusion>
                    <groupId>com.google.guava</groupId>
                    <artifactId>guava</artifactId>
                </exclusion>
            </exclusions>
</dependency>