Snippets of my settings.xml:

   <mirror>
     <mirrorOf>central</mirrorOf>
     <url>http://penguin.nanometrics.ca:8081/repository</url>
     <id>nmx-central-mirror</id>
     <name>Mergere Mirror Repository</name>
   </mirror>

   <profile>
     <id>maestro</id>
     <repositories>
       <repository>
         <id>maestro-project-server</id>
         <name>Maestro Project Server</name>
         <url>http://penguin.nanometrics.ca:8081/repository</url>
       </repository>
     </repositories>
     <pluginRepositories>
       <pluginRepository>
         <id>maestro-project-server</id>
         <name>Maestro Project Server</name>
         <url>http://penguin.nanometrics.ca:8081/repository</url>
       </pluginRepository>
     </pluginRepositories>
   </profile>

nicolas de loof wrote:
The browsing is rendered by archiva.

What URL did you provide as miror ?

2007/3/29, Ben Tatham <[EMAIL PROTECTED]>:

Oh wait...I spoke to soon.  Now it got the artifact directly from
repo1.maven...That's what I don't want.  Argg...

Nico, does setting the guest to Observer affect how it accesses
.../repository?  When I go to the website and look at /repository, I get
a directory listing.  Is that just standard tomcat doing that or is it
archiva making that page for me?

-Ben

nicolas de loof wrote:
> Your right about the "download on request" behaviour :
> Archiva will ask the proxied repositories for any artifact missing in
the
> managed repository.
>
> You need to grant the "guest" user the observer role so that it can
> download
> artifacts. Maybe this is the issue you get.
>
> Nico.
>
>
> 2007/3/29, Ben Tatham <[EMAIL PROTECTED]>:
>>
>> Hello All,
>> I am trying to use archiva on our company network to "proxy" the
central
>> repos...my understanding is that this means that if a developer runs
>> Maven and requests an artifact from the archiva repository, that if
>> archiva does not already have it in its own repository, it will get it >> from the global repo (or mirror) and put it in its repo, and give it to >> the local maven request. That way, the next developer that comes along
>> does not have to go out to the net to get it.  Is this correct?
>>
>> If this is the expected behaviour, it does not seem to work for
me.  Any
>> ideas?  Below is my archiva.xml.
>>
>> Thanks in advance,
>> Ben <cid:part1.02000705.07090602@nanometrics.ca>
>>
>> <?xml version="1.0" encoding="UTF-8"?><configuration>
>>   <repositories>
>>     <repository>
>>
>> <directory>/disk1/maestro-1.1
>> /project-server/data/project-server/repository</directory>
>>       <includeSnapshots>true</includeSnapshots>
>>       <id>maestro</id>
>>       <name>Central Managed Repository</name>
>>     </repository>
>>   </repositories>
>>   <proxiedRepositories>
>>     <proxiedRepository>
>>       <url>http://repo.mergere.com/maven2</url>
>>       <managedRepository>maestro</managedRepository>
>>       <snapshotsPolicy>hourly</snapshotsPolicy>
>>       <releasesPolicy>hourly</releasesPolicy>
>>       <useNetworkProxy>true</useNetworkProxy>
>>       <id>mergere</id>
>>       <name>Mergere Repository Mirror</name>
>>     </proxiedRepository>
>>     <proxiedRepository>
>>       <url>http://www.ibiblio.org/maven2</url>
>>       <managedRepository>maestro</managedRepository>
>>       <snapshotsPolicy>daily</snapshotsPolicy>
>>       <useNetworkProxy>true</useNetworkProxy>
>>       <id>Ibiblio</id>
>>       <name>Ibiblio</name>
>>     </proxiedRepository>
>>   </proxiedRepositories>
>>   <localRepository>/root/.m2/repository</localRepository>
>>
>> <indexPath>/disk1/maestro-1.1
>> /project-server/data/project-server/index</indexPath>
>>   <proxy>
>>       <host>primrose</host>
>>       <port>8080</port>
>>   </proxy>
>> </configuration>
>>
>>
>




Reply via email to