I imagine there have to be a number of projects/companies out there
using Maven artifacts and incurring bandwidth costs to build systems.
Atlassian seems to be recommending the practice to its Bamboo users...

http://confluence.atlassian.com/display/BAMBOO/Populating+your+EBS+volume#PopulatingyourEBSvolume-UploadingMaven2repositorydata

I know its not much, but on large builds and continuous integration
projects would benefit.

What's the current storage requirements for the central repository at this time?

I wonder if the maven central repo could qualify as a public dataset?
http://aws.amazon.com/publicdatasets/
http://developer.amazonwebservices.com/connect/forum.jspa?forumID=55

Mark

On Sun, Dec 20, 2009 at 8:28 PM, Carlos Sanchez <car...@apache.org> wrote:
> there was some talk about it during ApacheCON but there are some costs
> associated
>
> - S3 storage of the EBS snapshot
> - bandwidth to upload the repo and keep it up to date
> - an EC2 machine to do the rsync and scheduled snapshots of the EBS volume
>
> There's an option to "sell" it so users end paying the fees
>
>
> On Sun, Dec 20, 2009 at 8:18 PM, Mark Diggory <mdigg...@gmail.com> wrote:
>> Cheers,
>>
>> After experimenting a bit with EC2, It seems it would be ideal if
>> there were an EBS volume that had all the Maven central repository
>> within it.  Does anyone know of such a thing?
>>
>> thanks,
>> Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Reply via email to