news <[EMAIL PROTECTED]> wrote on 07/02/2003 06:00:32 AM: > 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.
The 'apache repository' and the ones maven can use (note that maven can have multiple repositories) are not necessarily one and the same thing. We have a 'repository' at a customer site I work on, as well as one at the office. Apache hosting its own (of whatever format is agreed) would be a good idea, IMHO. Having it mirrored would also be good. > 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. Sure, but let's not lose focus of what this is for. Distribution? Building? A company/individual can set up their own repository of jars (we all do) that they've accepted licenses for. The 'tools' should be able to work with that set up, similar to how Maven does today. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
