No, you're misreading the code.
The plugin has several commands: one generic that should list all runtimes
plus additional ones limited to certain runtuimes (requested by the Camel
team).
Look at the retrieved catalog (
https://forge.api.openshift.io/api/booster-catalog), Quarkus is not there
I think that's because the author of that extension seems to have
hard-coded the list of available runtimes:
https://github.com/redhat-developer/vscode-project-initializer/blob/master/src/extension.ts#L11-L16
That ain't good - if our primary tools accessing this assume everything
is static
On Thu, Apr 23, 2020 at 1:25 PM Christophe Laprun
wrote:
> I think (?) there used to be an api to Launcher. Is it still available?
>
Yes this is the one that's being used in Project Initializer and JBoss
Tools Launcher wizard. But there is no Quarkus runtime there, any reason
it's only through
Thanks Max, this is great news!
I think this was the biggest hurdle to adoption of Launcher, so I'm really
pleased to see that the team has been able to reach consensus on this. The
long list of names you mention attests to how deceptively complex this
change is.
Paul.
On Wed, Apr 22, 2020 at
