Re: URI Syntax was: Repository
Nick Chalko wrote: ... What should the URI look like The latest URI discussed was http://host/project/version/artifact-[version].ext For example * http://repo.apache.org/org-apache-ant/1.5.1/ant-1.5.1.jar * http://repo.apache.org/org-apache-ant/1.5.1/ant-testutil-1.5.1.jar * http://repo.apache.org/org-apache-ant/1.5.1/LICENSE.txt This is where Avalon keeps jars for the framework similar to the above example (done by Leo after the previous repo discussions IIUC): http://www.apache.org/dist/avalon/framework/jars/avalon-framework-4.1.jar http://www.apache.org/dist/avalon/framework/jars/avalon-framework-impl-4.1.5.jar http://www.apache.org/dist/avalon/framework/jars/LICENSE.txt So it's: http://host/project/artifact-type/artifact-[version].ext host: www.apache.org/dist project: avalon/framework artifact-type: jars httpd instead does this: http://www.apache.org/dist/httpd/ Please note this URL: http://www.apache.org/dist/httpd/binaries/aix/apache_1.3.26-000964804C00-ibm-aix4.3.tar.gz It could be: host: www.apache.org/dist project: httpd artifact-type: binaries/aix The tar.gz format is more complex, and needs a different version resolution system. -- Nicola Ken Barozzi [EMAIL PROTECTED] - verba volant, scripta manent - (discussions get forgotten, just code remains) -
How to reference projects in the Repository.
Here is the goals I think we shouould have for a project reference scheme. * Human Readable * globaly unique * stable over long periods of time If these are reasonable goals, then we should start evalutating the merrits of different approaches. R, Nick smime.p7s Description: S/MIME Cryptographic Signature
Re: URI Syntax was: Repository
Nick Chalko [EMAIL PROTECTED] wrote on 31/10/2003 08:38:36 AM: Since this is an ASF repo, isn't the ASF project name enough? I think I would still prefix it with apache, so that other organizations can follow our pattern with out conflicts. Also allowing other repositories to host artifacts from multiple orginizations. Sounds like a good idea. There is still some naming details to work out. An apache project can be a very big thing. Take the CLI project in Jakarta commons that would be apache-jakarta-commons-cli vs the pacakge name org.apache.commons.cli This is where the previous naming convention breaks for me. site/project/version/artifact-version.type assumes that the 'project' has a single versioning system. Jakarta as a project doesn't. e.g. commons/beanutils has versions very different from commons/logging. *As an example only*, maven treats commons/beanutils and commons/logging as two separate projects. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ Pub Key:http://blogs.codehaus.org/people/dion/public-key.asc