archiva-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter.Pilg...@ubs.com
Subject RE: Proxy vs. Repository URLs
Date Tue, 28 Nov 2006 11:02:22 GMT

> -----Original Message-----
> From: Joakim Erdfelt [mailto:joakim@erdfelt.com] 
> 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.
> 
> consider the following
> 
> <repository>
>   <id>snapshots</id>
>   <url>http://archiva.corporate.com/repository/snapshots</url>
> </repository>
> 

(1)


> vs
> 
> <repository>
>   <id>corporate.snapshots</id>
>   <url>http://archiva.corporate.com/repository/snapshots</url>
> </repository>
> 

 (2)

And your point is? What is different then apart from the identifier
name? Is (1) is supposed to 
better than (2) or is it vice versa?


> 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.
> 
==////==
--
Peter Pilgrim
UBS Investment Bank, 
PTS Portal / IT FIRC OPS LDN,
100 Liverpool Street, London EC2M 2RH, United Kingdom
+44 (0) 20 75 75692
:: Java EE / E-Commerce / Enterprise Integration / Development ::
 

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.


Mime
View raw message