Carlos Sanchez wrote:
eg. we require that if you have a foo.com domain your groupId is
com.foo but after that it's up to you. If you have a foo.sf.net we
require net.sf.foo but no more than that.
I like this one very much. It's in-line wit Sun's guidelines for package
names, and provides a good balance between structure and flexibility.
From the erlier e-mails it seems that you are planning to map the
groupIds to repository directories hierarchy: net.sf.foo -> /net/sf/foo.
On a large servers this might become a performance bottleneck because of
the number of entries in the TLD directories (/org etc). A faster
approach would be something like /org/a/apache/... or even
/org/ap/apache/... This should be handled transparently to the users -
the group id should be org.apache.... in either case. A
/repository-metadata.xml or similar could contain information necessary
for building correct paths. It's probably in the domain of Wagon if I
understand things correctly.
R.
PS. You are going such great job guys! I'm looking forward to the
upcoming 1.1 release.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
