On Thu, 2003-02-06 at 14:00, Costin Manolache wrote: > 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 want it to be common for all Java projects not just Apache. The repository is for _all_ Java projects and the needs of majority of Java developers outweighs the needs of simply Apache. I think you should take a little more time and actually ask some questions. I don't think you really understand what we're trying to do. Everything you outline above is _exactly_ what we've been trying to do. But now that everyone has figured out that this is indeed a good idea it's somehow bad that it's all in the Maven repository? Why? > ( 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. For God's sake Costin please ask some questions before assuming what capabilities are in Maven. We have multiple repositories, to deal with most situations that arise. Kurt also had discussions with Ted about using a PORTS like system. We've discussed many of these things. Just because you're getting involved now please don't presume to know what we have planned or what we have implemented. To toss out the -1, even though not binding, without much backgroud information is shows heavy bias. And that's fine, just be honest about it. > > Costin > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
