Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket pipeline maven dependency 308 error


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 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 ( Failed to transfer file with status code 308 -> [Help 1]
[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] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]

3 answers

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.

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

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

<name>Grails core</name>

That didn't resolve it for me.

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.

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events