URL Name was introduced to make the repository snippets make sense. consider the following
<repository> <id>snapshots</id> <url>http://archiva.corporate.com/repository/snapshots</url> </repository> vs <repository> <id>corporate.snapshots</id> <url>http://archiva.corporate.com/repository/snapshots</url> </repository> One future feature for archiva is to manage the pom internal repositories to point to itself. In other words, if archiva is told to proxy central, and a pom gets pulled down pointing to a new repository of say ... <repository> <id>sf.net</id> <url>http://projfoo.sourceforge.net/maven2/</url> </repository> then archiva should replace that entry with itself so that the requests at the maven client continue to hit the corporate repository. We need to have a more sane / verbose id field, as that is what is used in maven client for log messages and the like. But having a more verbose id field for the url make no sense. hence the split. For the record, I don't like the /proxy/ servlet in archiva. It has no security!! It will be removed. And the /repository/${urlname}/ will have the proxy abilities (with security) - Joakim Erdfelt Henri Yandell wrote: > On 11/24/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: >> Consider the following managed repository: >> >> My Managed Repository >> Identifier MYREPO >> Directory >> E:\svn\maven\archiva\archiva-webapp\target\my-managed-repository >> WebDAV URL http://localhost:9091/repository/myrepo >> Type Maven 2.x Repository >> Snapshots Included true >> Indexed true >> >> To use it as a normal repository, the url is >> http://localhost:9091/repository/myrepo >> >> To use that same repo as a proxy, (as far as I can tell, with maxb's >> help on IRC,) it's >> http://localhost:9091/proxy/MYREPO >> >> Is this correct? If so, why do we use the 'URL Name' in one place and >> the 'Identifier' in another? > > +1 to using the identifier in both. > > Hen >
