Bandwidth costs to mirror Maven repositories: $50
File server to store it on: $1500
Developer effort to access the internal repository: $200
Having 20 developers sit around idle because you didn’t mirror the java.net repository: priceless
With apologies to Mastercard.
Author: Robert Watkins
My name is Robert Watkins. I am a software developer and have been for over 20 years now. I currently work for people, but my opinions here are in no way endorsed by them (which is cool; their opinions aren’t endorsed by me either). My main professional interests are in Java development, using Agile methods, with a historical focus on building web based applications. I’m also a Mac-fan and love my iPhone, which I’m currently learning how to code for.
I live and work in Brisbane, Australia, but I grew up in the Northern Territory, and still find Brisbane too cold (after 22 years here). I’m married, with two children and one cat. My politics are socialist in tendency, my religious affiliation is atheist (aka “none of the above”), my attitude is condescending and my moral standing is lying down.
View all posts by Robert Watkins
3 thoughts on “Why external Maven repositories are a bad idea”
You said it perfectly, the culprit of the above Mastercard story is _you_, not Maven.
I never said it wasn’t me.
yes you generally only make that mistake once 😉 Shame it isn’t trivially easy to create a local shared repo with one flick of the command line (I could be wrong).
But, in cases like that, there is only one thing you can do, one word, three letters: pub.