Bitbucket pipeline maven dependency 308 error

[raywee]

My pipeline is suddenly failing with a Maven dependency 308 (permanent redirect) error. There has been no change to that or it's upstream dependency, and the build runs fine locally. I've also verified the existence and accessibility of the artifact, and do not see any redirects when accessing from my browser.  I've tried re-running over several days, but no cigar. using maven:3.6.1-jdk-8

Any help much appreciated!

Here's the error:

[ERROR] Failed to execute goal on project rhythm-domain-services: Could not resolve dependencies for project com.xxx:jar:4.2.0: Failed to collect dependencies at net.sf.jasperreports:jasperreports:jar:6.11.0 -> com.lowagie:itext:jar:2.1.7.js7: Failed to read artifact descriptor for com.lowagie:itext:jar:2.1.7.js7: Could not transfer artifact com.lowagie:itext:pom:2.1.7.js7 from/to jaspersoft-third-party (http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/): Failed to transfer file http://jaspersoft.jfrog.io/jaspersoft/third-party-ce-artifacts/com/lowagie/itext/2.1.7.js7/itext-2.1.7.js7.pom with status code 308 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

[raywee]

As it turns out, it was a problem with one of the 3rd party lib dependency repos with 6.11 of jasperreports... suddenly went offline or something corrupted... updated to 6.17 and all good now.

[Michał]

I had version 6.16 and after upgrade to 6.17 problem is gone. Thanks for help.

[Robrecht Minten]

I had the same issue. Adding following repo to my pom file resolved my problem.

<repository>
    <id>Grails-core</id>
    <name>Grails core</name>
    <url>https://repo.grails.org/grails/core/</url>
</repository>

[Greg Galbreath]

That didn't resolve it for me.

[Robrecht Minten]

I solved it by resolving other problems in the pom file. The error that was shown, wasn't the actual problem. As stated below, check your dependencies.

[Michał]

I have exactly the same error code 308 with jaspersoft third-party-ce-artifacts. I'm using maven:3.6.3-jdk-8.

Last successful build pipeline was in June 12th and from June 15th pipeline is always failed with this error.

[Tamiko Camp]

Same here, so watching for a reply as well. 

http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException slope game