Attached is an archive which shows a sample repository structure where the product-specifier contains >= 2 path segments.
Hopefully, this will carify things. It contains: . ant versions 1.5.2, 1.5.3-1, 1.5.4 and nightlies of 1.6alpha . httpd 2.0.48 . jms 1.1 . jndi 1.2.1 . commons-collections 1.0, 2.0 . commons-cli 1.0, nightlies of 1.0 and 2.0 . commons-betwixt 1.0-alpha-1, nightlies of 1.0-beta-1-dev (all sample files are empty) -Tim > From: Tim Anderson [mailto:[EMAIL PROTECTED] > > > From: Nick Chalko [mailto:[EMAIL PROTECTED] > > > > Tim Anderson wrote: > > > > > > > >>The fact that commons-lang and commons-io are both part of the same > > >>Jakarta Project has no meaning to a repository. > > >> > > >> > > > > > >True, but users browsing the repository can find them easier if > > >they are grouped together. > > > > > > > > > > > The only difference between > > commons/lang and commons-lang is the number of items in a directory. > > > > but again if we allow arbitrary number of "/" before the the artifact > > part how can we tell what the project is we are back to > > http://repo.com/alpha/beta/alpha/beta/dist/beta-alpha.zip > > http://repo.com/dist/nightly/dist/dist/dist/dist/foo.zip > > > > Silly examples but with out a RIGID spec it will happen. Someone will > > want to name thier project Alpha, or nightly or the orginaztion will > > be named dist or intrim or snapshot. > > > > Lets just pick a number of groupings one or two or three and stick with > > it. > > Allow the "/" to have special meaning. > > > > R, > > Nick > > > > The distinction between organisation and project would no longer exist: > repository-uri = access-specifier "/" product-specifier "/" > version-specifier "/" artifact-specifier > product-specifier = path_segments > > i.e, the organisation, project, subproject etc, are encoded in the URI > using 1-n path segments. > > To ensure that reserved words aren't included in product-specifier, > it would need to be specified as: > product-specifier = path_segments & ~reserved > reserved = formal-build-designation | interim-build-designation > | latest > formal-build-designation = "release" > interim-build-designation = "interim" | "nightly" | "snapshot" | ... > > This means: > . tools cannot parse organisation, project etc details from the URI > . tools can extract product-specifier, version-specifier, and > artifact-specifier by parsing right to left. >
Description: Binary data