-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
quarkus:run to support arguments and property setting #46001
Labels
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
kind/enhancement
New feature or request
Comments
We could do what we do in DevMojo: /**
* Allows configuring arbitrary JVM arguments. Multiple arguments can be specified by delimiting them with a space
* character.
*/
@Parameter(defaultValue = "${jvm.args}")
private String jvmArgs;
@Parameter(defaultValue = "${quarkus.args}")
private String argsString;
@Parameter
private Map<String, String> environmentVariables = Map.of();
@Parameter
private Map<String, String> systemProperties = Map.of(); |
We actually have |
@maxandersen do you want to try #46011? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/devtools
Issues/PR related to maven, gradle, platform and cli tooling/plugins
kind/enhancement
New feature or request
Describe the bug
quarkus:run does not seem to support setting properties nor command line arguments.
command line
mvn quarkus:dev -Dquarkus.args=". ~/code
result in "." and "~/.code" being passed as arguments to the running app butmvn quarkus:run -Dquarkus.args=". ~/code"
seem to have no effect.quarkus run
also does not seem to honor it. I would expectquarkus run -- . ~/code
or similar to work as a way to pass in arguments but I thnk because neither maven nor gradle supports a wayquarkus run
is not able to do it.properties
Not sure how this should work to be honest as quarkus:run is meant to be running the app fairly isolated but somehow
mvn -Dquarkus.someproperty -Dfileserver.paths=.. quarkus:run
would be nice to honor ...but also not sure blindly sending all build system properties over to quarkus:run is meaningful.if not, we should at least document to use .env or env variables instead.
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: