You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since my jdtls config seems to be broken on the newly published v1.28.0, I wanted to back to v1.27.1:
{ 'jdtls', version = '1.27.1' }
Unfortunately the installation fails as in the mason-registry, there is a hard-coded timestamp in the url which corresponds only to v1.28.0. Interpolating the version into the url:
https://download.eclipse.org/jdtls/milestones/{{ version | strip_prefix "v" }}/jdt-language-server-{{ version | strip_prefix "v" }}-202309281329.tar.gz
leads to an invalid url.
UPDATE: I just noticed that Mason actually provides an API to install older versions, I will report this issue there directly. I am pretty sure that this is more of an issue in the mason-registry, but since they don't expose a public API to regress to older versions it is not really a "bug" from masons perspective.
Are you aware of this issue and do you a way to work around it?
The text was updated successfully, but these errors were encountered:
The eclipse repositories provide a file latest.txt for each version. Maybe the mason registry should only link to https://download.eclipse.org/jdtls/milestones/{{ version | strip_prefix "v" }} and derive the full path by looking into the correponding latest.txt file to avoid this issue. But I'm not familiar enough with the internals of Mason and mason-registry to know whether this is feasible.
Since my jdtls config seems to be broken on the newly published v1.28.0, I wanted to back to v1.27.1:
{ 'jdtls', version = '1.27.1' }
Unfortunately the installation fails as in the mason-registry, there is a hard-coded timestamp in the url which corresponds only to v1.28.0. Interpolating the version into the url:
leads to an invalid url.
UPDATE: I just noticed that Mason actually provides an API to install older versions, I will report this issue there directly.
I am pretty sure that this is more of an issue in the mason-registry, but since they don't expose a public API to regress to older versions it is not really a "bug" from masons perspective.Are you aware of this issue and do you a way to work around it?The text was updated successfully, but these errors were encountered: