Joakim Erdfelt wrote:
> 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 ...
>
> sf.net
> http://projfoo.sourceforge.net/maven2
> -Original Message-
> From: Joakim Erdfelt [mailto:[EMAIL PROTECTED]
> Sent: 27 November 2006 13:32
> To: archiva-users@maven.apache.org
> Subject: Re: Proxy vs. Repository URLs
>
> URL Name was introduced to make the repository snippets make sense.
>
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 ...
sf.net
http://projfoo.sourceforge.net/maven2/
then archiva should replace tha
URL Name was introduced to make the repository snippets make sense.
consider the following
snapshots
http://archiva.corporate.com/repository/snapshots
vs
corporate.snapshots
http://archiva.corporate.com/repository/snapshots
One future feature for archiva is to manage the pom intern
On 11/24/06, Henri Yandell <[EMAIL PROTECTED]> wrote:
> 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.
Then why have the "URL Name" at all?
--
Wendy
On 11/24/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Consider the following managed repository:
My Managed Repository
Identifier MYREPO
DirectoryE:\svn\maven\archiva\archiva-webapp\target\my-managed-repository
WebDAV URL http://localhost:9091/repository/myrepo
Type
