Answers inline. On Thu, Jun 4, 2009 at 3:50 PM, scabbage<[email protected]> wrote: > > - What if the central repo goes down? We'll end up with broken builds and > the QEs will go crazy at us!
There are a few things about this that bug me. Maven only downloads from central once for released artifacts. So, the build server and most likely all of the developers will have copies of all required jars in their ~/.m2/repository directory. So if central is down, and you aren't dependent on any SNAPSHOTs, as long as the build doesn't include a new dependency, then you probably won't even notice. Furthermore, I've been using maven for a couple of years now and I don't remember even so much as a planned outage of central. IIUC, central is mirrored all over the world, one server being down probably just means it gets taken out of rotation and no one notices. The "what if" style arguments are a PITA... What if the cold war starts back up and our colo facility gets nuked?!! Will the builds fail? Of course they will, but I prefer to worry about making my day-to-day easier than worrying about all of the things that *could* make it harder. > - Ok, so we can have proxies, but then we have to maintain them. Lots of > work. See my answer to question 1. Rather than a proxy, get nexus. I run a repository manager for myself and my team in my office, as well as one at home. It's not that much work at all. > - Not checked into CVS??? That's not good. Not comfortable without having a > complete set of artifacts in a SAFE place. Not comfortable! Who says things aren't checked into CVS? As I mentioned before, you will end up with all of the jars you need distributed on machines all over your network. In fact, that is one of the things I have had to deal with before. Since ~/.m2 translates to c:\Documents and Settings\Username on modern windows machines, a few developers ended up with roaming profiles exceeding a few gigabytes. Anyhow, I can't force you to be comfortable with something, but if you must, then just have the build server check-in it's ~/.m2 directory on a regular basis. > - Your pom.xml only shows those dependencies your project is directed > dependent upon. Fine. But what about all other dependencies that your > dependencies depend upon? Know who they, get them and put in CVS!! You can check-in the ~/.m2 if it's a requirement. I think many people will agree that it's a waste of time, but YMMV. > > Not sure if any of you have encountered these challenges. Please give me > some suggestions. -- Wes Wannemacher Author - Struts 2 In Practice Includes coverage of Struts 2.1, Spring, JPA, JQuery, Sitemesh and more http://www.manning.com/wannemacher --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
