The URL to download the latest build has changed with the recent upgrade to Nexus 3.x

[ndoschek]

Our CI workflow started failing with the following error when running the check in review mode via @eclipse-dash/nodejs-wrapper:

https://github.com/eclipse-theia/theia/actions/runs/23050264141/job/66949391384?pr=17151

INFO: Fetching dash-licenses...
100  1381  100  1381    0     0   3257      0 --:--:-- --:--:-- --:--:--  3264
ERROR: Downloaded dash-licenses jar file appears to be invalid or corrupted

The downloaded file is only 1381 bytes, which suggests an error page rather than the actual JAR. I tested the download URL from the README directly in the browser and it returns a 404:

https://repo.eclipse.org/service/local/artifact/maven/redirect?r=dash-licenses&g=org.eclipse.dash&a=org.eclipse.dash.licenses&v=LATEST

This is similar to past access issues with repo.eclipse.org (#466) afaics.

Could you help getting this fixed? Thanks in advance!

[adharsh0713]

I was able to reproduce the issue locally.

---

1. Redirect endpoint used by the wrapper returns 404

Command:

curl -Uri "https://repo.eclipse.org/service/local/artifact/maven/redirect?r=dash-licenses&g=org.eclipse.dash&a=org.eclipse.dash.licenses&v=LATEST" -Verbose

Result:

HTTP 404 Not Found

---

2. Maven metadata endpoint works

Command:

curl -Uri "https://repo.eclipse.org/content/repositories/dash-licenses/org/eclipse/dash/org.eclipse.dash.licenses/maven-metadata.xml" -UseBasicParsing

Result:

StatusCode: 200

Metadata shows:

<release>1.1.0</release>

---

3. Direct artifact download works

Command:

curl -Uri "https://repo.eclipse.org/content/repositories/dash-licenses/org/eclipse/dash/org.eclipse.dash.licenses/1.1.0/org.eclipse.dash.licenses-1.1.0.jar" -OutFile dash.jar

Verify:

Get-Item dash.jar

Result:

Length : 15581113

(~15 MB valid JAR)

---

Conclusion

• The artifact and repository are working correctly.
• The failure appears to be specific to the Nexus redirect endpoint:

/service/local/artifact/maven/redirect

Since the wrapper relies on this endpoint, it downloads the HTML error page (~1 KB) instead of the JAR, which triggers the corruption error in CI.

---

Possible Improvement

To make the wrapper more robust, it could resolve the version via maven-metadata.xml and construct the artifact URL directly instead of relying on the redirect endpoint.

Happy to help with a fix if that approach makes sense.

[waynebeaton]

@ndoschek it appears that your script uses https://github.com/eclipse-dash/nodejs-wrapper

AFAICT, the problem is caused by the recent upgrade of repo.eclipse.org from Nexus 2 to Nexus 3.x.

The URL that obtains the latest release uses the search functionality from Nexus 2, which has been replaced in version 3.x.

AFAICT, the URL should now be:

https://repo.eclipse.org/service/rest/v1/search/assets/download?sort=version&repository=dash-maven2-releases&maven.groupId=org.eclipse.dash&maven.artifactId=org.eclipse.dash.licenses&maven.extension=jar

I'll update the README with the new URL and open an issue on https://github.com/eclipse-dash/nodejs-wrapper
to update the nodejs wrapper.

I'll also check in with the team to see if there is something that we can do to make a more resilient URL.

FYI @marcdumais-work

[waynebeaton]

I've created an issue in the Eclipse HelpDesk.

[waynebeaton]

Hey @adharsh0713

Please accept this as constructive criticism.

Happy to help with a fix if that approach makes sense.

It doesn't.

I assume that your intentions are good and I appreciate your attempt. However, AFAICT there is a very high probability that your response was entirely generated by an AI and have no confidence that you actually understand the issue.

Again, I assume that your intentions are good, appreciate that you want to help, and understand that you're trying to build reputation to help build a case for your GSOC application. But this sort of engagement actually makes it harder for open source maintainers.

[adharsh0713]

Thanks for the clarification and for pointing out the Nexus 3 API change.

I had reproduced the 404 locally but didn't realize that the redirect endpoint belonged to the Nexus 2 API that was removed during the upgrade.

Apologies if my earlier comment caused extra work.

[ndoschek]

Thanks a lot for looking into this @waynebeaton and opening the issues!