Discussions
Categories
- 384.6K All Categories
- 2.5K Data
- 556 Big Data Appliance
- 1.9K Data Science
- 451.4K Databases
- 222.1K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 32 Multilingual Engine
- 562 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 561 SQLcl
- 4K SQL Developer Data Modeler
- 187.5K SQL & PL/SQL
- 21.4K SQL Developer
- 296.9K Development
- 1 Application Development
- 18 Developer Projects
- 140 Programming Languages
- 293.6K Development Tools
- 112 DevOps
- 3.1K QA/Testing
- 646.2K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 193 Java Community Process
- 106 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 21 Java Essentials
- 166 Java 8 Questions
- 86K Java Programming
- 81 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 206 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 536 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 178 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 236 Portuguese
Publish Oracle Dev Tools to the OpenVSX registry
Hi there,
The Oracle Developer Tools extension is published on Microsoft's VS Code Marketplace, which makes it available to lots of people. This, sadly, excludes anyone who uses VS Code by running from source, using projects like VS Codium or utilizing VS Code from within places that integrate it (like Gitpod, Eclipse Theia). These projects have to use another marketplace (due to Microsoft's Terms of Service) and most of them have settled on the vendor-neutral FOSS OpenVSX registry.
It would be great if the extension could be in there too, enabling it for hundreds of thousands of developers who currently cannot access it from their workflows.
It would be best if Oracle could publish the extension themselves, because it would really simplify the whole process.
If there's already an automated process in place to publish to Microsoft's Marketplace, publishing to OpenVSX should be super-easy. OpenVSX has a CLI. ovsx, that behaves very similarly to vsce.
There are docs about the publishing process in the OpenVSX GitHub Wiki and I am willing to assist in any problems that might arise in the publishing process.
Best Answer
-
Hi, we are working towards publishing there. If you work for the Eclipse Foundation, please contact me at christian (dot) shay (at) oracle (dot) com.
Answers
-
Hi, we are working towards publishing there. If you work for the Eclipse Foundation, please contact me at christian (dot) shay (at) oracle (dot) com.
-
@Christian.Shay -Oracle I personally don't work for Eclipse, but I have forwarded this to the team there. Someone should shoot you an email soon :)
-
Thank you. Are you the lead developer/owner for any of the projects using OpenVsx? If so, could you also email me?