I sent a message to maven-dev, and according to J Van Zyl, ibiblio already "pulls" from Apache. I'm not exactly sure how this works.

What is the next step in creating the repository directory? I'm a bit confused at to the Apache formalities. Are these mirroring issues a huge deal or can we go ahead, create the directory, and start building to it?

Thanks!


A discussion started about creating a Maven repository on an ASF machine, to increase the ease of availability for nightly builds and new releases.

Here are the relevant threads:
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=563250
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&by=thread&from=580195


Here was a suggestion:


> Why not discuss the following with the Maven guys over at iBiblio:

 > a directory at Apache that an iBiblio account [even possibly the
 > current Maven repo?] rsyncs files from.

 > This allows us to push things to the apache version, then iBiblio
 > becomes the bandwidth holder [by making the apache one vaguely
 > authenticated].


What do you guys think about this?

> I am working on the general process of automating uploads to ibiblio
> in general so once the set of tools are done the Apache folks can use > the same tools.


> In the meantime a simple directory structure would work as ibiblio
> already pulls from Apache. Maybe you can kick their collective asses
> but the whole thing basically turned into a subterfugre to develop
> another piece of software and bring it to Apache. If they actually
> wanted a Maven repository that sync'd with Ibiblio it would take
> exactly 10 minutes of work.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to