EclipseFdn / EclipseFdn/publish-extensions
Extension `vscode-gradle` not up-to-date after repo migration
- Dominant language
- JavaScript
- Stars
- 341
- Forks
- 428
- Avg merge
- 40m
- Merged PRs (30d)
- 2
Description
Hi there!
The extension [`richardwillis.vscode-gradle`](https://open-vsx.org/extension/richardwillis/vscode-gradle) migrated to a [Microsoft repo](https://github.com/microsoft/vscode-gradle) (now: [`vscjava.vscode-gradle`](https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-gradle)). While it has already been [added to extensions.json](https://github.com/open-vsx/publish-extensions/commit/440d6a9ff944035510a3a8c317548eb61736469a), it's [not available](https://open-vsx.org/extension/vscjava/vscode-gradle). This was [briefly discussed](https://github.com/open-vsx/publish-extensions/issues/591#issuecomment-1301190252) in November 2022, apparently without resolution. It seems sensible to mention [the issue asking Microsoft to publish vscode-gradle to Open VSX](https://github.com/microsoft/vscode-gradle/issues/1369).
The extension remains published under the old namespace with an old version, which is probably undesirable all around.
I am not personally involved in any of this, other than being an end-user noticing a discrepancy after finding an interesting-looking extension. Some questions this raises for me, though:
1. Could there be an automatic check on the server-side of Open VSX whether a GitHub repo is redirecting to a new owner, and at least mark it as an actionable item?
2. Is there a process at Open VSX for when a self-published extension goes inactive or canonically changes owner?
3. What can I expect to happen regarding the inclusion of `vscjava.vscode-gradle`?
Contributor guide
Assessment
This issue has not been assessed yet.