Manuel Carrasco Moñino

@marcushellberg does it happens always? I mean each time you stop and start the application, or only once at the beginning?

The only way I have managed to reproduce it is by removing the following block from the `pom.xml` file and removing the folder `~/.m2/repository/com/vaadin/vaadin-maven-plugin/24.4.0.beta1/` ``` vaadin-prereleases https://maven.vaadin.com/vaadin-prereleases ``` Then the...

So in summary, in both cases the `mvn vaadin:configure` was not executed correctly @gtzluis logs happen in the same code line, perhaps some problem with `mvn` in local, and in...

Good point. Yes callback is being implemented in https://github.com/vaadin/vaadin-connect/issues/55, does it covers the customisation you meant?

@knoobie source is now available in public repo

There is already an internal ticket for this https://github.com/vaadin/control-center/issues/924

I guess this is fixed, can we close @jojule ?

> I’m wondering what the reason for this model was @aloubyansky We did in this way mainly for simplicity. The official Quarkus extension (vaadin-quarkus) already lived in its own [repository](https://github.com/vaadin/quarkus)...

Thanks, @aloubyansky, you're right, our vaadin-quarkus-extension setup isn't a standard Quarkus extension. Here's the reasoning: We have an unified platform release, thus, we repackage vaadin-quarkus so everything in the Vaadin...

I have seen this message before when building platform o flow-components that are using parallel execution, but we have not experienced any problem, so we just ignore the message, has...