I'm not quite sure what's happening there - the proxy shouldn't rely
on the indexer to have run. Worth checking.
- Brett
On 02/10/2006, at 5:21 PM, Mohni, Daniel wrote:
Hi all,
I just want to inform everyone that this is working now.
I installed the mail-1.3.2.jar manualy in the 3p_repo and
tryed to access it using
http://archiva/proxy/3p_release/javax/mail/mail/1.3.2/mail-1.3.2.jar
this was only working after I run the indexer manualy.
-> don't forget to run the indexer after you install files manualy
- Daniel
-----Original Message-----
From: Mohni, Daniel [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 27, 2006 3:53 PM
To: [email protected]
Subject: proxying multiple repositories
Hello
Archiva is now running fine for the default repository.
I have configured 2 different repositories one for the
internal artefacts and one for thirdparty artefacts that
are currently not available in a maven repository.
I have configured a profile in my settings.xml like this
<profile>
<id>Repository Proxy</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<repositories>
<repository>
<id>maven-release</id>
<url>http://archiva:8080/archiva/proxy/maven_release</url>
</repository>
<repository>
<id>internal-release</id>
<url>http://archiva:8080/archiva/proxy/internal_release</url>
</repository>
<repository>
<id>3p-release</id>
<url>http://archiva:8080/archiva/proxy/3p_release</url>
</repository>
</repositories>
</profile>
the first repository added after creating the admin was
'maven_release',
and this is proxied to http://repo1.maven.org/maven2/
Artefacts in this repository will be found and can be accessed using
the ../archiva/proxy/maven_release/..
but the artefacts in the other repositories are not delivered,
does someone has a similar working setup ?
tnx
Daniel
