-
Notifications
You must be signed in to change notification settings - Fork 27
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
Debugging no-starter code projects fails #389
Comments
Yup, I can reproduce :
|
rgrunber
added a commit
to rgrunber/vscode-quarkus
that referenced
this issue
Aug 30, 2021
- Adjust task pattern to recognize build output when no starter code is present - Fixes redhat-developer#389 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber
added a commit
to rgrunber/vscode-quarkus
that referenced
this issue
Aug 31, 2021
- Adjust task pattern to recognize build output when no starter code is present - Fixes redhat-developer#389 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber
added a commit
to rgrunber/vscode-quarkus
that referenced
this issue
Aug 31, 2021
- Adjust task pattern to recognize build output when no starter code is present - Add pattern to detect task has ended on failed launch - Fixes redhat-developer#389 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber
added a commit
to rgrunber/vscode-quarkus
that referenced
this issue
Sep 1, 2021
- Adjust task pattern to recognize build output when no starter code is present - Add pattern to detect task has ended on failed launch - Fixes redhat-developer#389 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
rgrunber
added a commit
that referenced
this issue
Sep 1, 2021
- Adjust task pattern to recognize build output when no starter code is present - Add pattern to detect task has ended on failed launch - Fixes #389 Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a no-starter code project (you still need to create 1 java file), if you execute the debug quarkus command, the process never completes.
This is mostly caused by the quarkus dev task's problemMatcher.background.endspattern value, that expects a "listening on" pattern.
vscode-quarkus/src/buildSupport/GradleBuildSupport.ts
Line 30 in 46b180e
vscode-quarkus/src/buildSupport/MavenBuildSupport.ts
Line 30 in 46b180e
When no http server is started, that last sentence is missing, it then just waits indefinitely.
Using
^.*Quarkus .* started in .*\\.*
works.Also, it doesn't seem to cause an issue but when a Gradle deamon is reused, this pattern is never found:
vscode-quarkus/src/buildSupport/GradleBuildSupport.ts
Line 29 in 46b180e
I'd simply use
Task :
insteadThe text was updated successfully, but these errors were encountered: