[EMAIL PROTECTED] wrote: > 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.
True. That's exactly my point. We need an Apache repository and a set of tools to be used in apache - and this should work for all projects and build tools that are in apache. We need a standard layout and descriptors for dependencies - but this needs to be agreed on by all involved. If maven scope is to create a build tool - that's perfect. If maven scope is both a build tool and an apache repository and non-apache repository and defining standards for other build tools - that's not good. Probably it would be a good idea if someone with experience in a standard process would get involved in the repository and descriptors- Geir or Craig would be great ideas ( I know many have issues with the JCP - but the fact remains that setting any standard is different than writing code ). Costin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
