Replies: 1 comment 1 reply
-
I found out that What DOES work on the other hand is setting the build property as environment variable:
This definitely changed in Quarkus 3. I will try to find some time and create a reproducible repository. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
My Quarkus project can be built as "server" or "worker" binary depending on the
mode
system property I give on the Gradle build commandline (example:-Pmode=worker
). The server binary should contain REST endpoints and a customJWTCallerPrincipalFactory
for validating JWTs. ThisJWTCallerPrincipalFactory
shall not be enabled for the worker binary because the worker does not provide REST endpoints. This is how theJWTCallerPrincipalFactory
bean looks like (just an excerpt):The
server.property
only has a value for the server build but none for the worker build. Since we updated the project to Quarkus 3 today we noticed that the worker binary doesn't start up properly any more (the server is running fine). The error is:So Quarkus 3 actually tries to set the properties to some values although there aren't any. Quarkus 2 did not complain about the missing value, either because it simply set
null
in this case or it actually didn't even try to set properties because the bean has been disabled by the@IfBuildProperty
annotation.Is this a known issue? I couldn't find anything in the Quarkus 3 migration guide about this. We're currently trying to set
defaultValues
for these properties, which should resolve the issue. But I still wonder why Quarkus tries to set properties on a bean that has been disabled during build time. Sounds like a bug to me.Beta Was this translation helpful? Give feedback.
All reactions