Replies: 1 comment
-
/cc @glefloch, @quarkusio/devtools |
Beta Was this translation helpful? Give feedback.
0 replies
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
we have a multi-project gradle build containing different quarkus applications and start them in parallel. We want to configure different quarkus profiles and debug ports per project based on environment variables.
We are using following simplified command to start in dev mode:
In our
build.gradle
files we have following content, used environment variables differ for each project:The problem: by setting the system properties like this causes other projects to sometimes use the system property of another project when started in parallel. This is probably due to the system property is being set for whole gradle process and not only for forked vms.
For quarkus profile we found that we could pass it via
jvmArgs
:However, this does not work with the debug property, because the debug value is directly read from
System.getProperty("debug")
https://github.com/quarkusio/quarkus/blob/main/devtools/gradle/gradle-application-plugin/src/main/java/io/quarkus/gradle/tasks/QuarkusDev.java#L420Is there another way to pass system properties only to quarkusDev task so it also works for
debug
?For spring it seems possible to set system properties only for
bootRun
task according to following issue (spring-projects/spring-boot#23578) :Is there something similar for quarkusDev? Or is there a better way to solve this problem?
Beta Was this translation helpful? Give feedback.
All reactions