I think the directory listing issue is known - you might need to check JIRA for it and file it if not. However, accessing the artifacts should work fine as it seems to be the case.
I'm not quite sure why you got inconsistent results since you used the mirrorOf - all requests should be going to the repository. But as you say, if you can access the files on the Archiva repository URLs, then Maven should be fine as it doesn't navigate the tree. - Brett 2008/10/8 Kraft, Mike <[EMAIL PROTECTED]>: > Well, I should have thought to do this earlier: I use a parent POM with > multiple child modules - I had added the 'public' repository to the parent > POM, but not the children. So I added it to the children, and now Maven finds > remote snapshots properly when I build a child directly. > > However, if that is the solution, it still does not explain why there was > never a problem finding release artifacts - surely Maven should have been > just as clueless about those in the absence of a <repository> listing in a > child POM? OTOH, perhaps that is a Maven rather than an Archiva issue. > > Finally, after looking more closely, the issue of what I see at the URL for > the 'public' group appears to be a directory listing issue in Archiva. Here's > an example of what I mean: > * my artifact 'widget' has two versions: 0.20.0 (from 'internal'), and > 0.21.0-SNAPSHOT (from 'snapshots'); > * the directory listing at > http://.../archiva/repository/public/widget/widget/ currently only shows the > SNAPSHOT, but not the release; > * but if I go directly to > http://.../archiva/repository/public/widget/widget/0.20.0 , the release > artifacts are there. > > So this is not serious, esp. since the 'Browse' view does show everything > properly, but it is a little annoying. > > Mike > > -----Original Message----- > From: Kraft, Mike [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 07, 2008 13:06 > To: [email protected] > Subject: FW: Repository group questions > > Ok, I get the feeling there is something fundamental I do not understand > about repositories. Although it took a while, sometime after I promoted > 'snapshots' to the top of the group list, the artifacts shown by the 'public' > URL changed to only show snapshots - no releases. OTOH, Maven still cannot > locate remote snapshot artifacts. But it can find remote release artifacts. > > If anyone can shed any light on this, I would be very appreciative. > > Thanks, > Mike > > ________________________________ > > From: Kraft, Mike > Sent: Tuesday, October 07, 2008 12:25 > To: [email protected] > Subject: Repository group questions > > > Hi, > > I have created a group 'public' that contains both the default 'internal' and > 'snapshots' repositories. I then created a mirror for * to 'public' in my > local settings. I noticed I was having some trouble locating snapshot > artifacts that were not already present in my local repository. So I began > looking at the settings for the 'public' group. I clicked through on the URL > link to the group, and saw that only artifacts from 'internal' showed up - > nothing from 'snapshots'. I tried changing the order of the two repositories > in the group list, but it did not seem to make any difference. > > Just to be clear, 'snapshots' itself is working - I see the unified view of > all the repositories when I go the 'Browse' page. > > Is the groups feature broken, or is it just some weird condition on my server? > -- Brett Porter Blog: http://blogs.exist.com/bporter/
