You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
It would be nice to be able to govern Quarkus build properties the same way you can govern mojo properties from the command line, like this for example:
Implementation ideas
Support Maven and Gradle properties as a build-time config source. The priority would be above the application.properties but below system and env. properties.
The text was updated successfully, but these errors were encountered:
Here is a challenge: it might be impossible to get ahold of the build system properties from within @QuarkusTest. That means that the augmentation that happens during this test phase doesn't have access to the same environment that "normal" augmentation has.
This is perhaps another reason to revisit the "last-minute" augmentation that is happening in tests and dev mode, maybe in favor of a test-augment phase.
Description
It would be nice to be able to govern Quarkus build properties the same way you can govern mojo properties from the command line, like this for example:
This is based on a rough idea that was discussed on the development list.
Implementation ideas
Support Maven and Gradle properties as a build-time config source. The priority would be above the
application.properties
but below system and env. properties.The text was updated successfully, but these errors were encountered: