Were you browsing your proxy repo via the Nexus Web GUI, or just the standard webserver directory listing?  Nexus lazily populates the storage of proxy repositories, so you won't see files appear in the webserver listings until the files are actually requested the first time.  However, you should be able to browse the downloaded JBoss.org index from within the Nexus Web GUI by selecting the repo, and then viewing the "Browse Index" tab.  If these don't work, you might check with the Sonatype guys on #nexus@codehaus.org

Experiencing the exact same problem using Nexus. Here is some additional information from nexus.log:

2011-04-11 06:36:18 WARN  [ool-1-thread-12] - o.s.n.i.DefaultInde~          - Cannot fetch remote index for repository public-jboss

java.io.FileNotFoundException: nexus-maven-repository-index.zip (item not found)

       at org.sonatype.nexus.index.DefaultIndexerManager$2.retrieve(DefaultIndexerManager.java:1095)

       at org.apache.maven.index.updater.DefaultIndexUpdater.loadIndexDirectory(DefaultIndexUpdater.java:190)

       at org.apache.maven.index.updater.DefaultIndexUpdater.access$300(DefaultIndexUpdater.java:75)

       at org.apache.maven.index.updater.DefaultIndexUpdater$LuceneIndexAdaptor.setIndexFile(DefaultIndexUpdater.java:641)

       at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:875)

       at org.apache.maven.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:156)

       at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:1111)

       at org.sonatype.nexus.index.DefaultIndexerManager.downloadRepositoryIndex(DefaultIndexerManager.java:1013)

       at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:897)

       at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:850)

       at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:824)

       at org.sonatype.nexus.tasks.ReindexTaskHandlerLegacy.reindexRepository(ReindexTaskHandlerLegacy.java:60)

       at org.sonatype.nexus.tasks.AbstractIndexerTask.doRun(AbstractIndexerTask.java:72)

       at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:192)

       at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:338)

       at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)

       at java.util.concurrent.FutureTask.run(FutureTask.java:138)

       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)

       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)

       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

       at java.lang.Thread.run(Thread.java:662)

Caused by: org.sonatype.nexus.proxy.ItemNotFoundException: The remoteURL we requested does not exists on remote server (remoteUrl="http://repository.jboss.org/nexus/content/groups/public-jboss/.index/nexus-maven-repository-index.zip")

       at org.sonatype.nexus.proxy.storage.remote.commonshttpclient.CommonsHttpClientRemoteStorage.retrieveItem(CommonsHttpClientRemoteStorage.java:248)

       at org.sonatype.nexus.index.DefaultIndexerManager$2.retrieve(DefaultIndexerManager.java:1078)

       ... 21 more

It would appear there is an issue retrieving the Nexus indexes for the public-jboss url. Any assistance, thoughts, dreams, or wishes are welcomed.

I was able to reproduce the two issues, the missing directories in the index, and the error in the "Browse Remote" tab.

According to Sonatype, the "Browse Remote" issue is a known bug, and will be fixed in Nexus 1.9.1.  See these jiras for more info:

https://issues.sonatype.org/browse/NEXUS-4150

https://issues.sonatype.org/browse/NEXUS-4225

I'm waiting to hear back from Sonatype about the missing hibernate-core issue.  I tried regenerating the index, but that didn't seem to have any effect.  I can also find the correct hibernate-core jars when using the Nexus search, so the info should be in the index, but I don't know why it's not browsable.  I'll post an update when I have more information.

Looks like the missing files in index browsing is also a known Nexus issue, and will be fixed in Nexus 1.9.1

https://issues.sonatype.org/browse/NEXUS-4186

Hi,

After upgrade to Nexus 1.9.2, I'm still unable to have my jboss repository proxies correctly configured.

I tried to add these proxies:

- https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/

Index is OK but unable to browse the repository via "Browse Remote" in Nexus GUI.

- https://repository.jboss.org/nexus/content/groups/public-jboss/

Remote Browsing is OK but unable to get the remote index.

Maybe this message from nexus log can help:

Aborted walking on repository ID='jboss-public' from path='/.index', cause: Item not found on path "/.index" in repository "jboss-public"!

- https://repository.jboss.org/nexus/content/repositories/releases/

For this proxy I have no problem, index and remote browsing are OK

Any idea about these issues ?

Thanks in advance

Correction for my last message:

An index is loaded for https://repository.jboss.org/nexus/content/groups/public-jboss/ but is incomplete.

Apparently the index of https://repository.jboss.org/nexus/content/repositories/releases/ is loaded in place of the complete public-jboss index.

I think the index issue in on the JBoss repo side.  Even if you upgraded to 1.9.2, the JBoss Nexus repo is still at 1.9.0.2, so we're still affected by the indexing issues that I listed above.  We don't have a date set for upgrade, because there are some additional fixes we are waiting for possibly in 1.9.3.