vscode-gradle icon indicating copy to clipboard operation
vscode-gradle copied to clipboard

Show gradle execution info in the log

Open CsCherrYY opened this issue 4 years ago • 1 comments

the gradle execution would be one of the following three:

  • Gradle wrapper
  • specific Gradle version
  • local Gradle installation

Will show specific gradle execution info in the log.

CsCherrYY avatar Aug 20 '21 05:08 CsCherrYY

Hi @CsCherrYY, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Suggestions to surface Gradle execution details in the log:

  • Enable debug-level traces for the language server to capture command invocations. For example, follow the approach in eclipse.jdt.ls to guard log messages with a debug flag:

    • See “Some log info should be debug traces” for using Platform.getDebugOption to toggle verbose logging: https://github.com/eclipse-jdtls/eclipse.jdt.ls/issues/2603
  • Verify and explicitly configure which Gradle distribution is used via VS Code settings:

    • java.import.gradle.wrapper.enabled (true to prefer wrapper)
    • java.import.gradle.version (to pick a specific version)
    • java.import.gradle.home (for a local installation)
    • Related discussion on how these settings interact and a workaround when using a local Gradle install: https://github.com/microsoft/vscode-gradle/issues/1025#issuecomment-938298913
    • Notes on wrapper vs. local home precedence in a restricted environment: https://github.com/redhat-developer/vscode-java/issues/1495#issuecomment-652885328

No direct duplicate found.

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

github-actions[bot] avatar Nov 06 '25 08:11 github-actions[bot]