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

Options set in "Run Task with Args" dialog with quotes are not passed correctly #1623

Open
thomasdelhomenie opened this issue Nov 7, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@thomasdelhomenie
Copy link

Extension Name: vscode-gradle
Extension Version: 3.16.2024102102
OS Version: Windows 10
VSCode version: 1.95.1 and 1.96.0-insider

Describe the bug
Options set in "Run Task with Args" dialog with quotes are not passed correctly, whereas it works fine in command line.

To Reproduce

  • Create a Gradle Java project
  • In the Gradle view, right click on the help > tasks task
  • Click on Run Task with Args
  • In the dialog, type --group=Verification
  • Press Enter -> the output is correct, only the tasks of the Verification group are displayed:
> Task :tasks

------------------------------------------------------------
Tasks runnable from root project 'test-vscode-run-task'
------------------------------------------------------------

Verification tasks
------------------
check - Runs all checks.
test - Runs the test suite.
  • Reexcute the task the same way but with --group="Verification" -> the output is incorrect:
> Task :tasks

------------------------------------------------------------
Tasks runnable from root project 'test-vscode-run-task'
------------------------------------------------------------

No tasks

whereas it works fine in both cases when executing it in command line.

Expected behavior
The options set with quotes should be passed correctly, and both commands should work fine, as when executed in command line.

Screenshots

Output from "Gradle for Java"

[info] [gradle-server] Gradle Server started, listening on 53270
[info] Gradle client connected to server
[info] Java Home: C:\Program Files\Eclipse Adoptium\jdk-17.0.8.101-hotspot
[info] JVM Args: --add-opens=java.base/java.util=ALL-UNNAMED,--add-opens=java.base/java.lang=ALL-UNNAMED,--add-opens=java.base/java.lang.invoke=ALL-UNNAMED,--add-opens=java.prefs/java.util.prefs=ALL-UNNAMED,--add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED,--add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED,--add-opens=java.base/java.nio.charset=ALL-UNNAMED,--add-opens=java.base/java.net=ALL-UNNAMED,--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED,-Xmx2g,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant
[info] Gradle User Home: C:\Users\tdelhomenie\.gradle
[info] Gradle Version: 8.10
[info] Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.10/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

CONFIGURE SUCCESSFUL in 7s
[info] Found 33 tasks
[info] Completed build: tasks
[info] Completed build: tasks --group="Verification"
[info] Completed build: tasks --group=Verification
[info] Completed build: tasks --group="Verification"

Does the bug still exist if you disable all other extensions?
Yes

Additional context

@thomasdelhomenie thomasdelhomenie added the bug Something isn't working label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant