Create a Quarkus Dev Explorer in the IDE

[ia3andy]

The first feature would be to see the list Quarkus apps and be able to:
start dev => open (in browser) | dev-ui (ide) | restart | stop (something should check if the dev-server is up)

Then later it could also:

• give a way to list/add/remove extensions
• check if the versions are up to date / trigger update
• see if the plugin is up to date (update)
• list resources with link to java code

[fbricon]

I just learned there's already a way to open the Dev UI from the console: https://quarkus.io/blog/intellij-quarkus-tools-1.12.0/#improved-quarkus-run-experience

[angelozerr]

Indeed I noticed that but it doesnt promote dev ui. If we have a tree item whuch shows devvui it will promote more

More this actions is shown for any console like lsp console and is available even if server is not started.

[ia3andy]

I just learned there's already a way to open the Dev UI from the console: https://quarkus.io/blog/intellij-quarkus-tools-1.12.0/#improved-quarkus-run-experience

Woooow this is the most hidden feature ever :)

[angelozerr]

@ia3andy I think the right direction is to use Services and not a custom view for Quarkus Explorer.

@fbricon said me that Spring support has migrated their custom String view to Services, see https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000428264-New-Spring-Boot-Run-dashboard-not-showing-up?page=1#community_comment_360000755240

[angelozerr]

The Services view show existing run config, so I think the first step is to auto create a Quarkus run config (according a settings) when project is imported. It will give the capability after importing a Quarkus project to go to Services view and see the Quarkus run config without creating it at hand.

The second step is to customize the tree of the Services to add for instance Open Dev UI action.

[angelozerr]

According @adietish, some user prefer having a custom view, see https://plugins.jetbrains.com/plugin/10485-kubernetes/reviews#review=74758

[ia3andy]

According @adietish, some user prefer having a custom view, see https://plugins.jetbrains.com/plugin/10485-kubernetes/reviews#review=74758

I also think the view is way more visible and allows more customization (like detecting if the dev-server is started)

[angelozerr]

@fbricon I think more and more than a custom Quarkus view is a better idea. The current PR is not perfect and should take care of tracking Quarkus run config to fill it with new Quarkus run config but I think it is not a big deal.

Perhaps we should start to provide a custom Quarkus view at first and see in the second step how to customize Services view with Quarkus.

@fbricon what do you think about that?