`buildNumber` is not propagated in dev mode

[rsvoboda]

buildNumber is not propagated in dev mode and DEV UI shows app version as null in the top right corner of http://localhost:8080/q/dev-ui/ and in http://localhost:8080/q/dev-ui/welcome

This behaviour is caused by #231 changes which sets the version based on the hash, buildNumber property is set to null in dev mode:

Hash works fine when running app in JVM production mode, here is the message from dev mode vs. production jvm mode:

2024-06-19 14:23:01,533 INFO  [io.quarkus] (Quarkus Main Thread) quarkus-bot on JVM (powered by Quarkus 3.11.2) started in 1.267s. Listening on: http://localhost:8080
    vs.
2024-06-19 14:30:02,608 INFO  [io.quarkus] (main) quarkus-bot 77f2357 on JVM (powered by Quarkus 3.11.2) started in 0.499s. Listening on: http://0.0.0.0:8080

I tried to propagate revision property same way as in 88d76b2 and expected value was visible in configuration editor.

Seems this all goes to buildnumber-maven-plugin and how it sets the buildNumber property. @gastaldi any tips on this?

[gastaldi]

That doesn't seem to be propagated from a ConfigSource during dev mode. As a workaround, you can do the same as I did in registry.quarkus.io: add buildNumber=999-SNAPSHOT to your local .env, which will display the version as 999-SNAPSHOT when in dev mode/tests