evolvedbinary repo

[miljanuscumlic]

@adamretter I don't know where is the best place to make this request, so I'll try it here (maybe it's better than on SO). Adam, could you please re-enable evolvedbinary repo and upload 3.4.0 artifact.

[miljanuscumlic]

This is from the nexus.log:

2017-07-29 15:28:12,109+0200 INFO  [pxpool-1-thread-1] admin org.sonatype.nexus.index.tasks.UpdateIndexTask - Scheduled task (Update eXist repository) started :: Updating repository index "eXist" from path  and below.
2017-07-29 15:28:12,359+0200 INFO  [pxpool-1-thread-1] admin org.sonatype.nexus.index.DefaultIndexerManager - Trying to get remote index for repository "eXist" [id=eXist]
2017-07-29 15:28:12,562+0200 INFO  [pxpool-1-thread-1] admin org.sonatype.nexus.proxy.storage.remote.httpclient.HttpClientRemoteStorage - Initializing remote transport for proxy repository "eXist" [id=eXist]...
2017-07-29 15:28:13,000+0200 INFO  [pxpool-1-thread-1] admin org.sonatype.nexus.index.DefaultIndexerManager - Cannot fetch remote index for repository "eXist" [id=eXist] as it does not publish indexes.

And after I changed the repo URL to the new one: http://repo.evolvedbinary.com/repository/exist-db/

2017-07-29 15:30:30,937+0200 INFO  [qtp18875015-54] admin org.apache.http.impl.execchain.RetryExec - I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://repo.evolvedbinary.com:80: The target server failed to respond
2017-07-29 15:30:30,937+0200 INFO  [qtp18875015-54] admin org.apache.http.impl.execchain.RetryExec - Retrying request to {}->http://repo.evolvedbinary.com:80

2017-07-29 15:31:40,656+0200 INFO  [pxpool-1-thread-3] admin org.sonatype.nexus.index.tasks.UpdateIndexTask - Scheduled task (Update eXist repository) started :: Updating repository index "eXist" from path  and below.
2017-07-29 15:31:40,812+0200 INFO  [pxpool-1-thread-3] admin org.sonatype.nexus.index.DefaultIndexerManager - Trying to get remote index for repository "eXist" [id=eXist]
2017-07-29 15:31:40,968+0200 INFO  [pxpool-1-thread-3] admin org.sonatype.nexus.index.DefaultIndexerManager - Cannot fetch remote index for repository "eXist" [id=eXist] as it does not publish indexes.

[adamretter]

@miljanuscumlic Sorry for the delay. I have now uploaded the remaining 3.4.0 artifacts to Nexus. If you have any problems please re-open the issue.

[miljanuscumlic]

@adamretter By the Github rules it seems I don't have enough privileges to reopen the issue. So I will add new comment here avoiding some noise in issues, hoping someone will see it.

I'm still not being able to get the artifacts and I am still getting aforementioned messages in the log like Cannot fetch remote index for repository "eXist" [id=eXist] as it does not publish indexes. Also, on my Routing tab for the eXist proxy repo in nexus interface I have:

Routing

Publishing

Status: Not published.
Message: Discovery in progress or unable to discover remote content (see discovery status).

Discovery

Status: Unsuccessful.
Message: No scraper was able to scrape remote (or remote prevents scraping).
Last run: Mon Aug 21 2017 11:14:24 GMT+0200 (Central Europe Standard Time)

So it seems Nexus 3 is quite a different beast to Nexus 2. We have now setup a task to enable the publishing of Maven Indexes for the eXist-db repo. This will happen every hour. We also just did a first-run and that seemed to complete OK, so can you please test again?

When I visit repo links with the browser I cannot see its contents directly without going through Nexus's component browser or asset browser, like I was able before your upgrade to Nexus 3.

I don't like that either, but unfortunately it was an intentional design choice in Nexus 3. If you Google you will find plenty of others complaining then can no longer browse the hierarchy via their Web Browser. However, that doesn't stop Maven itself from working correctly.

[miljanuscumlic]

@adamretter I've tested it again, and it works just fine. Thank you Adam for your continuous support. I highly appreciate it.