-
Notifications
You must be signed in to change notification settings - Fork 146
Add ability to set JVM args when using executable Java apps #888
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
Conversation
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.
Pull Request Overview
This PR adds support for passing JVM arguments to executable Java applications in the Community Toolkit. The enhancement allows developers to configure JVM-specific options (like system properties, memory settings, etc.) when using AddJavaApp for executable Java resources.
- Adds
JvmArgsproperty toJavaAppExecutableResourceOptionsclass - Updates executable Java app creation to prepend JVM arguments before the
-jarcommand - Updates test to verify correct argument ordering
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/CommunityToolkit.Aspire.Hosting.Java/JavaAppExecutableResourceOptions.cs |
Adds new JvmArgs property with XML documentation |
src/CommunityToolkit.Aspire.Hosting.Java/JavaAppHostingExtension.Executable.cs |
Implements logic to prepend JVM arguments to command line |
tests/CommunityToolkit.Aspire.Hosting.Java.Tests/ExecutableResourceCreationTests.cs |
Updates test to include JVM args and verify correct argument ordering |
|
@dotnet-policy-service agree |
Closes #887
This pull request introduces an additional
JvmArgsproperty toJavaAppExecutableResourceOptionswhich enables passing JVM arguments to executable Java apps when usingAddJavaApp.This is a non-breaking change.
PR Checklist
Other information