Can't browse repositories

[Ni...@le-rsi.fr]

Greetings,

 

I installed Archiva 1.1.3 and I'm running it deployed in JBoss 5.0. As
far as the webapp is concerned, every thing seems to work properly.

 

I added the Codehaus and the JBoss maven 2 repositories to the ones
configured by default, I created a network proxy as required by my
network and I created proxy connectors for all the configured
repositories. I did all this as admin. Once I finished, I clicked to the
Browse button and the < Browse repositories > page displays empty.

 

Trying to use maven with archiva doesnn't work (maven times out).
Without archiva maven is working. The settings.xml file only contains
the network proxy config, the same as the one in archiva.

 

Could anyone please help ?

 

Many thanks in advance,

 

Nicolas

 

 

Re: Can't browse repositories

[Wendy Smoak <ws...@gmail.com>]

On Mon, Feb 23, 2009 at 6:47 AM,  <Ni...@le-rsi.fr> wrote:

> I added the Codehaus and the JBoss maven 2 repositories to the ones
> configured by default, I created a network proxy as required by my
> network and I created proxy connectors for all the configured
> repositories. I did all this as admin. Once I finished, I clicked to the
> Browse button and the < Browse repositories > page displays empty.

That would make sense -- there is no content in your managed
repository yet.  There won't be any content until you either deploy
something, or request some artifacts that get proxied through.

> Trying to use maven with archiva doesnn't work (maven times out).
> Without archiva maven is working. The settings.xml file only contains
> the network proxy config, the same as the one in archiva.

The settings.xml only contains the network proxy config?  I assume
this is your "without archiva" configuration, which is working.

What is your "with archiva" settings.xml configuration?  You'll need
to add <repositories> and optionally <mirrors>.

-- 
Wendy

RE: Can't browse repositories

[yanke <ya...@dplanet.ch>]

As Wendy explained using
http://[server:port]/archiva/repository/[repoid]/org/apache/struts/struts2-core/2.1.6/struts2-core-2.1.6.jar
should trigger a download from the proxied repo to your local one (and then
you can see the file downloaded when browsing)

when you use :
http://10.82.0.39:8080/archiva/central/org/apache/struts/struts2-core/2.1.6/struts2-core-2.1.6.jar

you mean that "central" is the name of YOUR repo ([repoid])

[repoid] is the name you have configured in archiva as "Repository group"

since central is also the name of the central maven repo I thought you might
have used the wrong one,

just my 2 cents,

bye,
Yanke



Nicolas.Duminil-2 wrote:
> 
> Sorry for the confusion, I was thinking that once a remote repository is
> defined and a proxy is attached to it, one may browse the repository. I'm
> probably mistaken, am I ?
> 
> Anyway, going to
> http://10.82.0.39:8080/archiva/central/org/apache/struts/struts2-core/2.1.6/struts2-core-2.1.6.jar
> 
> both with the browser and wget says 404.
> 
> But I need to mention that on my Suse server, where archiva is installed,
> I cannot browse the net as the proxy is configured in such a way that it
> blocks any http request not having an IE user-agent. Could that be a
> problem while the maven and eclipse user-agent work properly ?
> 
> -----Message d'origine-----
> De : Wendy Smoak [mailto:wsmoak@gmail.com] 
> Envoyé : lundi 23 février 2009 17:54
> À : users@archiva.apache.org
> Objet : Re: Can't browse repositories
> 
> On Mon, Feb 23, 2009 at 9:25 AM,  <Ni...@le-rsi.fr> wrote:
> 
>> The point is that in the archiva webapp the browse page is empty. Meaning
>> that the repositories are never scanned. Meaning that something with the
>> network is wrong, but not the proxy config as it works without archiva.
>> Got it ?
> 
> You haven't mentioned putting anything in the repositories, so I
> expect them to be empty.  Just setting up a proxy connector won't do
> it... you can't browse through to the entire contents of the proxied
> repos, you will only see the contents of your managed repos, once
> artifacts have been deployed or proxied.
> 
> Try constructing a url to an artifact you know is in the remote repo
> but not in your managed repo, such as:
> http://[server:port]/archiva/repository/[repoid]/org/apache/struts/struts2-core/2.1.6/struts2-core-2.1.6.jar
> 
> Does that work in a browser or with wget?  (Note that this url is
> straight to the managed repo, it does not have /browse/ in it.)
> 
> -- 
> Wendy
> 
> 

-- 
View this message in context: http://www.nabble.com/Can%27t-browse-repositories-tp22161790p22967157.html
Sent from the archiva-users mailing list archive at Nabble.com.