Problem with setting up proxy repository on nexus

[alex_g]

Hi everyone, I am trying to use the maven classloader from JBoss DNA. This is the dependency I want to add to my project:

 <dependency>
 <groupId>org.jboss.dna</groupId>
 <artifactId>dna-classloader-maven</artifactId>
 <version>0.4</version>
 </dependency>

To do that first tried to import the jboss repository into our nexus repository as a proxy. I believe the proxy did not work because it failed to download the remote index. This is what I get in the nexus logs:

2009-05-07 09:28:10.028 INFO [pxpool-1-thread-9:] - org.sonatype.nexus.feeds.FeedRecorder:default: Reindexing repository with ID=JBoss : Process started on Thu May 07 09:28:09 CEST 2009, not yet finished.
2009-05-07 09:28:10.356 INFO [pxpool-1-thread-9:] - org.sonatype.nexus.index.IndexerManager:default: Trying to get remote index for repository JBoss
2009-05-07 09:28:11.716 WARN [pxpool-1-thread-9:] - org.sonatype.nexus.index.IndexerManager:default: Cannot fetch remote index:
java.io.IOException: Item not found nexus-maven-repository-index.properties
 at org.sonatype.nexus.index.DefaultIndexerManager$1.retrieve(DefaultIndexerManager.java:963)
 at org.sonatype.nexus.index.updater.DefaultIndexUpdater.downloadIndexProperties(DefaultIndexUpdater.java:216)
 at org.sonatype.nexus.index.updater.DefaultIndexUpdater.fetchAndUpdateIndex(DefaultIndexUpdater.java:70)
 at org.sonatype.nexus.index.DefaultIndexerManager.updateRemoteIndex(DefaultIndexerManager.java:977)
 at org.sonatype.nexus.index.DefaultIndexerManager.updateIndexForRemoteRepository(DefaultIndexerManager.java:860)
 at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:750)
 at org.sonatype.nexus.index.DefaultIndexerManager.reindexRepository(DefaultIndexerManager.java:692)
 at org.sonatype.nexus.DefaultNexus.reindexRepository(DefaultNexus.java:1397)
 at org.sonatype.nexus.tasks.ReindexTask.doRun(ReindexTask.java:47)
 at org.sonatype.nexus.scheduling.AbstractNexusTask.call(AbstractNexusTask.java:147)
 at org.sonatype.scheduling.DefaultScheduledTask.call(DefaultScheduledTask.java:345)
 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 at java.util.concurrent.FutureTask.run(Unknown Source)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 at java.lang.Thread.run(Unknown Source)

I thought my problem might be related to this thread: http://nexus.sonatype.org/mailing-list-user-archives.html#nabble-td23031611, but I tried using strict checksum policy and that didn't work either.

I have also tried inserting this to my project's pom file, with no effect:

<repositories>
 <repository>
 <id>JBOSS</id>
 <name>JBoss Repository</name>
 <url>http://repository.jboss.org/maven2/</url>
 </repository>

Finally, I even tried following the recommended procedure, i.e. I added to my settings.xml file the profile given here: http://www.jboss.org/file-access/default/members/dna/freezone/docs/0.4/manuals/gettingstarted/html/downloading_and_running.html

I can't get to download the dependency to my project with any of these methods. Please help??

[alex_g]

OK I found a solution to my problem. After adding the jboss.repository profile to my settings.xml file, I also defined the repository as a mirror, like so:

 <mirror>
 <id>jboss</id>
 <mirrorOf>jboss.repository</mirrorOf>
 <url>http://repository.jboss.com/maven2</url>
 <name>jboss</name>
 </mirror>

and it worked! Don't ask me why or how.

[rhauch]

Alex,

Glad that it finally worked. I'm not sure why the problem showed up in the first place, nor why the mirror fragment worked. I guess jboss.com is handled differently than jboss.org.

Best regards,

Randall

[timkroeger]

I know this is an old thread but I stumbled upon it having the exact same problem and searching for a solution. It turns out I just failed to configure nexus properly. You need to add the proxy repository to your public group before artifacts will be resolved for your additional repo. It's not sufficient to just add a proxy repository. And yes, I registered today just to dig out this ancient thread.

Cheers

Tim

[rhauch]

Tim, thanks for signing up and sharing the solution with all of us.