-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Allow quarkus:run to launch DevServices #40273
Conversation
geoand
commented
Apr 25, 2024
•
edited
Loading
edited
- Closes: Introduce DevServices in quarkus:run Maven goal #40270
@@ -52,7 +52,7 @@ public void defaultJavaCommand(PackageConfig packageConfig, | |||
List<String> args = new ArrayList<>(); | |||
args.add(determineJavaPath()); | |||
|
|||
for (Map.Entry<?, ?> e : System.getProperties().entrySet()) { | |||
for (Map.Entry<?, ?> e : System.getProperties().entrySet()) { //TODO: this is almost certainly wrong as it pulls in all the system properties Maven has set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we could select only those that are found on the command line. There is also some relevant code in DevMojo. E.g. we have systemProperties
as a Maven plugin goal parameter.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hm... As this is code that runs in the Quarkus build system, I am wondering if we should use BuildSystemTargetBuildItem.buildSystemProps
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that should be it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good point, it will rely on a Maven-specific env var to get the command line
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we could enhance it later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So do you propose I add it or not? Gotcha
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now I need to figure out hot to import the gradle plugins into IntelliJ :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tested the Gradle change as well
Status for workflow
|