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
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:
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?
Is there a process at Open VSX for when a self-published extension goes inactive or canonically changes owner?
What can I expect to happen regarding the inclusion of vscjava.vscode-gradle?
The text was updated successfully, but these errors were encountered:
Hi there!
The extension
richardwillis.vscode-gradle
migrated to a Microsoft repo (now:vscjava.vscode-gradle
). While it has already been added to extensions.json, it's not available. This was briefly discussed in November 2022, apparently without resolution. It seems sensible to mention the issue asking Microsoft to publish vscode-gradle to Open VSX.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:
vscjava.vscode-gradle
?The text was updated successfully, but these errors were encountered: