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

Change Gradle debug preLaunchTask's command and startPattern #134

Closed
xorye opened this issue Nov 4, 2019 · 0 comments · Fixed by #144
Closed

Change Gradle debug preLaunchTask's command and startPattern #134

xorye opened this issue Nov 4, 2019 · 0 comments · Fixed by #144
Assignees
Labels
bug Something isn't working gradle Issues related to Gradle support
Milestone

Comments

@xorye
Copy link
Contributor

xorye commented Nov 4, 2019

When debugging a Gradle Quarkus project using the Debug current Quarkus project command, a new task (that runs the Gradle quarkusDev command) will be created in .vscode/tasks.json if one does not exist already.

The automatically generated task has an incorrect problemMatcher[0].background.beginsPattern.
Instead of ^.*Scanning for projects...*, I suggest ^.*Starting a Gradle Daemon*.

Also, the Gradle commands located in command and windows.command should have the --console=plain flag added to them. This ensures that problemMatcher[0].background.beginsPattern and problemMatcher[0].background.endsPattern can match properly with the command's output.

This is important because if the end pattern fails to match, the debugger will not attach

@xorye xorye added bug Something isn't working gradle Issues related to Gradle support labels Nov 4, 2019
@fbricon fbricon added this to the 1.2.0 milestone Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working gradle Issues related to Gradle support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants