Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Maven and Gradle properties as a build-time config source #3012

Closed
dmlloyd opened this issue Jun 27, 2019 · 1 comment · Fixed by #3137
Closed

Support Maven and Gradle properties as a build-time config source #3012

dmlloyd opened this issue Jun 27, 2019 · 1 comment · Fixed by #3137
Labels
kind/enhancement New feature or request
Milestone

Comments

@dmlloyd
Copy link
Member

dmlloyd commented Jun 27, 2019

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:

mvn install -Dquarkus.native-image.jni=true

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.

@dmlloyd
Copy link
Member Author

dmlloyd commented Jul 2, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants