Flow: Vaadin Flow should be supported by Quarkus.io

[sandronm]

Because the Quarkus project allows live reload of jar, this could be really usefull to improve the Vaadin development experience.

https://quarkus.io/

If it is already possible, please create a tutorial explaining how to configure our project :-)

[pleku]

Yes, we'll definitely look at this at some point in the near future, but not a top priority at the moment.

Live reload is already possible with Vaadin using the Hotswap agent, spring-boot-devtools or JRebel. Quarkus could bring additional benefits and might be preferred if you use it already, but just to get live reload for development time it is not necessary.

[moewes]

I've made a POC with quarkus 0.20 und Vaadin 13. You may take a look at https://github.com/moewes/quarkus-vaadin-lab

[DemiusAcademius]

The final version of Quarkus has already been released:
https://quarkus.io/blog/quarkus-1-0-0-Final-bits-are-here/
and also exists:
https://github.com/Nano-Vaadin-Demos/nano-vaadin-quarkus
official expansion will bring a brighter future :)

[sanderPostma]

Vote-up
I was able to make the vaadin-demo-business-app working on Vaadin14 in production mode using & tweaking moewes's POC.
dev-mode is more difficult. After adding ServletBuildItem.builder .addInitParam("project.basedir", ...) .addInitParam("vaadin.frontend.token.file",...) in VaadinProcessor it starts up, but still getting lots of nasty errors in the browser console.
It would be better if someone experience debugging the Vaadin client side gave it a try. Maybe there are just a few things missing.

[mbrem]

Vote-up
I was able to make the vaadin-demo-business-app working on Vaadin14 in production mode using & tweaking moewes's POC.
dev-mode is more difficult. After adding ServletBuildItem.builder .addInitParam("project.basedir", ...) .addInitParam("vaadin.frontend.token.file",...) in VaadinProcessor it starts up, but still getting lots of nasty errors in the browser console.
It would be better if someone experience debugging the Vaadin client side gave it a try. Maybe there are just a few things missing.

Hi Sander
I've improved the Extension-POC and I've tried to implement a version of Vaadin-CDI in it (not yet finished ;) ). The Vaadin-demo-business-app is running with it (only production-mode / in dev-mode is an issue with bundling the client-bundle) and you can take a look on them under:

https://github.com/urosporo/vaadin-quarkus-extension-parent
https://github.com/urosporo/vaadin-demo-business-app/tree/V14

[sanderPostma]

Vote-up
I was able to make the vaadin-demo-business-app working on Vaadin14 in production mode using & tweaking moewes's POC.
dev-mode is more difficult. After adding ServletBuildItem.builder .addInitParam("project.basedir", ...) .addInitParam("vaadin.frontend.token.file",...) in VaadinProcessor it starts up, but still getting lots of nasty errors in the browser console.
It would be better if someone experience debugging the Vaadin client side gave it a try. Maybe there are just a few things missing.

Hi Sander
I've improved the Extension-POC and I've tried to implement a version of Vaadin-CDI in it (not yet finished ;) ). The Vaadin-demo-business-app is running with it (only production-mode / in dev-mode is an issue with bundling the client-bundle) and you can take a look on them under:

https://github.com/urosporo/vaadin-quarkus-extension-parent
https://github.com/urosporo/vaadin-demo-business-app/tree/V14

I had something very similar based on the project from moewes. I needed to add some extra init-params
See draft-pr

dev mode is starting without backend errors now, but the browser console still looks nasty. It does show the webpack:// & webpack-internal:// sources though.
When dev-mode is not working you can't really use Quarkus functions, but have to build something that you can debug on a more conventional app server and that -also- works on Quarkus.

[jhult]

Related issue: #9713

It looks like @mvysny is building an example project here: https://github.com/mvysny/vaadin-quarkus