>-----Original Message----- >From: Ron Wheeler [mailto:[email protected]] > >On 02/11/2010 3:29 PM, Haszlakiewicz, Eric wrote: >>> -----Original Message----- >>> From: Ron Wheeler [mailto:[email protected]] >>> The guys with small disk can just delete their entire local repo and let >>> maven rebuild it by itself from your central server which should have >>> lots of space. >>> One or two builds usually gets us back to a fast build from localhost. >> To delete the repo of the guy the next desk over I need to wait for him >to be in the office, then email or call him, then explain what I want him >to delete. And that's all only if I actually notice that that's what's >taking up all the space. >> Even if I'm just cleaning up my own files, why should I have to spend all >this time thinking about it and doing things to fix it? >> For example, I don't have to think about clearing out the cache in my >browser, why should maven's cache be any different? > >Each of my guys is responsible for his own workstation. They know what >maven is doing.
Gee, it must be nice to work with a whole group of maven geniuses. The people I work with are busy writing code and their time is better spent on that than having to remembering to perform basic maintenance on the build tool. As for workstations, I don't care about what people do on their individual PCs. That's not where the problem is. >>> If your central server is short of space spend $100 and add a terabyte >or >>> 2. >> Oh, are you going to fund the additional disk space, and the extra backup >resources needed, and pay for time it takes to actually update the disk >array and provision the space in my company's SAN? If so, great! >> My point it that using more disk space has more costs than just the price >of a drive platter. >You are right. > >I am not sure that a Maven Repo really belongs in a corporate datacentre >since it contains nothing that can not be replaced and is mostly stuff >that comes from outside sources anyway. > > You could always move your repo to the cloud and pay a few dollars per >month for the storage or just add a local desktop server to the >development group. What are you talking about? I thought this conversation was about the files that maven stores in the ~/.m2 directory. How could that possibly NOT be in the "corporate datacenter" if that's where everyone is doing development (and release builds)? FWIW, no I *can't* just add a local desktop server. For one thing it wouldn't do any good b/c not everyone would be able to get to it (we're not all sitting in the same room, nor even the same country!). Furthermore, that would be a huge headache since it would be outside of all of the procedures we've set up to have consistent environments, periodic backups, etc... eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
