« Using EJB3 with Spring
If it quacks like a startup, it is a startup… »

Why external Maven repositories are a bad idea

By Robert. Filed in Java  |  
Tags: ,
TOP del.icio.us digg

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.

This entry was posted on Thursday, April 5th, 2007 at 9:09 AM and is filed under Java. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.

3 Comments

  1. Comment by JJ Halloway:
    Thursday, April 5th 2007 at 10:10 AM | 

    You said it perfectly, the culprit of the above Mastercard story is _you_, not Maven.

  2. Comment by Robert:
    Thursday, April 5th 2007 at 10:22 AM | 

    I never said it wasn’t me.

  3. Comment by Michael Neale:
    Friday, April 6th 2007 at 3:09 PM | 

    hahahahaha…

    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.

Trackbacks / Pingbacks