George Gastaldi
George 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...
I can confirm this also happens in 1.30.1
@angelozerr I get this error when opening the https://github.com/quarkusio/quarkus project in IntelliJ
@angelozerr after updating the exception message no longer appears to me
@xian75 hey! That looks interesting. Do you have the beta version available somewhere so we can look?
Adding the links here, so I don't miss them: - https://github.com/xian75/sagacqrs/ - https://github.com/xian75/orchestrator-ABC/ - https://github.com/xian75/participant-A/ - https://github.com/xian75/participant-B/ - https://github.com/xian75/participant-C/ Any chance to make them public so others can chime in?
> @gsmet I am not sure how to check this. You mentioned "drop the local registry artifact" - how do I do that ? I cleared my .quarkus and .jbang...
@phillip-kruger can we somehow hit the registry when the UI to add an extension is opened?
Closing as the extension should not be part of core
@fbricon yes, it is supported in MP Config