Hi gang,

On 05-01-2005 09:39, "Nicola Ken Barozzi" <[EMAIL PROTECTED]> wrote:
> What relationship does the repository list have with Maven?
> What relationship does Maven have with the repository list?
> 
> Ass Brett Porter has written, and I agree:
> "
> 1) Maven PMC takes ownership for getting the repository right

IIRC [EMAIL PROTECTED] is actually a President's committee sort-of "hanging
off" infra@ that's been tasked with figuring all this stuff out. The reason
its not just the Maven PMC in the first place is that there's some other
people that have something to say as well (i.e. precisely the people listed
below). So I don't get why there's an ownership issue to reconsider. The
maven PMC peeps to work on this (Brett, Mark, anyone else who volunteers)
just get on the repository mailing list and JFDI.

> 2) Henk, myself (Maven PMC), Mark Diggory (if available), representative
> from interested Apache projects PMC (most likely someone from Ant) get
> together to sort out exactly what we think needs doing (we can use the
> repository list if appropriate)

Yep, sounds like a good idea.

> 3) suggest small steps to fix each problem rather than coming up with a
> killer solution that will never get implemented

Sounds like a good idea too. I'm guessing this is why I bailed out of that
mailing list in the first place; we were solving too big a problem at once.

> 4) can use the repository wiki for information based on what has already
> been discussed

And again, sounds like a good idea.

> I'd add that to use a common repository, there needs an implementation
> for all projects to use.

The [EMAIL PROTECTED] project was not tasked to deal with that. I think this
conflicts with #3.

Maven has support, ant will have support, magic (from the DPML guys) has
support, several ant-based scripts are around that provide support. Any tool
that can HTTP GET can trivially be made to get files from the repository.
For example I think I've done the basics in python, ruby, and bash+wget+grep
every now and then.


Cheers,


- Leo


Reply via email to