Custom maven repository error handler


(Matthew Prenger) #1

One of the maven repositories we are required to use is hosted on Amazon AWS. The problem with this is that it returns a 403 when a resource is missing, rather than a 404 (Annoying? yes, but we can’t do anything about it). This causes the error message that Gradle generates to be misleading.

Is there a way to override this so that Gradle treats 403’s the exact same as 404’s? Ideally only for this one repository, but for the whole project would probably be fine.


(Benjamin Muschko) #2

I don’t think there’s a way to do this at the moment.