James Taylor wrote: >> Maven is a nice tool - and I wish it good luck wherever it goes. >> But if Maven charter will include the creation of a maven-only repository >> - I hope at least some board members will vote -1. > > Hopefully we can keep these as seperate issues. Maven already has a > repository which can be used by any project, but might be considered > Maven (the project) only since access for uploading jars is currently > restricted. This is the case only because we are still developing the > administration application to open the repository up. The repository we > have now is neccesary to continue development of maven (the tool), but > nobody expects it to be the final solution. > > I would hate for this to prevent Maven's promotion to a top level > project, which I think is a step in the right direction for the project, > even if we still have a way to go, particularly with regard to a common > repository.
I am talking about this in the context of the other discussions on having an apache repository ( and use the apache mirroring system, etc). Also in the context of having a common policy on how releases will be distributed and structured - to fit well in such a repository. And the set of tools and conventions that are needed to access the repository. I agree moving maven to a top level ( apache or jakarta ) is the best step, but the common repository must be common to apache, and not maven specific. ( I know that everyone can use maven repository already ) BTW, given the license discussions it seems unlikely a solution that includes all the jars in the same place will work. So the "repository" will be not only a storage for jars, but a set of tools to deal with downloading from different locations with different methods ( and mirror lists, etc ). Again - I think this part can only be apache-wide. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
