adangel
commented
1 month ago What I could offer is, to publish this extension also as pmd.apex-pmd on VS Code Marketplace. That means, the same extension would be available at:
- https://marketplace.visualstudio.com/items?itemName=chuckjonas.apex-pmd
- https://marketplace.visualstudio.com/items?itemName=pmd.apex-pmd (doesn't exist yet...)
- https://open-vsx.org/extension/pmd/apex-pmd
(Some time ago, I created the "pmd" publisher namespace - https://marketplace.visualstudio.com/publishers/pmd)
Would that work? Then you could use a single name pmd.apex-pmd for both registries.
The extension under the new publisher "pmd" will start with 0 downloads, etc. See also https://github.com/Microsoft/vscode/issues/3670 - there is way to transfer an extension to a different publisher. Regardless which method is used - the extension will have a different id, which means, that users need to uninstall the old extension and install the new one.
Describe the bug Hi there! This is from Salesforce VS Code team.
apex-pmdis part of Salesforce VS Code Expanded Pack. We recently found a discrepancy of the entries for apex-pmd in Open VSX and VS Code Marketplace. In VS Code Marketplace it ischuckjonas.apex-pmdwhereas in Open VSX Registry it ispmd.apex-pmd.apex-pmd is the only extension within the expanded pack has the different entries for Marketplace and Open VSX Registry. We only publish a single version of expanded pack, so that makes the installation from Open VSX unable to find apex-pmd previously. We just checked in a fix but that is kind of an undefined behavior of VS Code - VS Code does not report any warnings or errors if the entry is not existed. We are still hoping apex-pmd could have a unified publisher.
Looking forward to your reply!