P2 proxy returns 404 for most files

Sonatype Nexus Repository
1

Hi,

We’ve been using nexus for a very long time and have recently upgraded from an older 3.x version to 3.28 OSS. In order to proxy our p2 repositories, we previously used the community plugin, but apparently nexus3 now supports p2 repositories out of the box.

Unfortunately, this doesn’t seem to work as expected.

Say for example we want to proxy the p2 update site for the “xtext” project like shown below:

xtext_p2
xtext_p21069×932 53.7 KB

Now that should give me the opportunity to access this file for example:

https://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.15.0/artifacts.xml.xz

however, when I try to access it via nexus, it returns me 404

http://nexus:8081/repository/eclipse-xtext/releases/2.15.0/artifacts.xml.xz

At least with the old community plugin, this has been working flawlessly for a very long time. I’ve tried to recreate the proxy and played with all imaginable settings, but all to no avail.

When I browse the proxied p2 repo, I can see a huge listing of directories named after an sha1 hash, but not the directory from the original repository seems to be missing.

Any ideas what’s wrong here?

2

There appears to be a composite p2 repository at the base URL you proxied, but Nexus does not maintain the path structure of the upstream web server.

If you use the base URL of the repository in Eclipse you should be able to access the contents of the composite site as well as all nested sites.

If you want to specifically access one of the repositories referenced by the composite site you should proxy it directly.