quarkus dev --dev-ui

[cescoffier]

Description

When you use an application that does not depends on vert.x HTTP, the dev UI is not available. That's sad :-(

We should be able to run the dev mode and get the dev UI. Three typical use cases:

• function (funqy)
• pure kakfa
• cli

Implementation ideas

\CC @iocanel @maxandersen

[quarkus-bot[bot]]

/cc @matejvasek (funqy), @patriot1burke (funqy), @phillip-kruger (devui)

[phillip-kruger]

We can maybe serve using the build in HTTP server ? And not vertx ? Would that even be possible ?

[iocanel]

@aloubyansky: I tried modifying the DevMojo and change the addQuarkusDevModeDeps method so that it also adds quarkus-vertx-http. I do see the dependencies and its transitives being resolved, but when the Dev mode starts the capability is still missing. Any ideas?

[aloubyansky]

They are not a part of the ApplicationModel. It seems the option would have to be added to the QuarkusBootstrapMojo.

[iocanel]

@aloubyansky even if get the DevMojo to extend the QuarkusBootstrapMojo and set the forced dependencies, it still does not work.

[aloubyansky]

Could you share the branch?

[iocanel]

Yeah

[iocanel]

@aloubyansky, here you are: https://github.com/iocanel/quarkus/tree/dev-ui-flag

Thanks in advance

[aloubyansky]

Adding dependencies in addQuarkusDevModeDeps isn't going to work, they won't end up in the model.

I was talking about an option (i.e. a mojo parameter) in the QuarkusBootstrapMojo. The model is resolved either in generate-code goal or dev. In case of the default config, the model will be resolved in the generate-code. Look at line 636 in DevMojo where extra params are passed to those goals. That'll cover the default config.

Then when the model has to be resolved in the DevMojo you could enforce these dependencies there.

[maxandersen]

@aloubyansky @iocanel where are we with this one ? is it feasible or we drop it?

[iocanel]

I don't recall if I ever got to try @aloubyansky advice.