che: [Quarkus] Can't debug Quarkus application

While testing vscode-quarkus extension I detected a problem: if execute Quarkus: Debug Current Quarkus Project command, I see a message: ERROR There is no debug configuration for undefined
in the browser console and the debugger doesn’t execute, but the configuration was generated in launch.json file:

   {
      "preLaunchTask": "quarkus:dev",
      "type": "java",
      "request": "attach",
      "hostName": "localhost",
      "name": "Debug Quarkus application",
      "port": 5005
   }

If try to run this configuration from Debug view, I see a message that Task 'quarkus:dev' terminated with exit code 127.

screenshot-che-che 192 168 99 104 nip io-2019 11 06-11_04_46 Probably this problem can be related to add support integratedTerminal for debugging https://github.com/eclipse-theia/theia/issues/6103

Che remote plugin with vscode-quarkus extension

apiVersion: v2
publisher: redhat
name: quarkus
version: 1.1.1
type: VS Code extension
displayName: Quarkus Tools
title: Quarkus Tools by Red Hat
description: This plug-in provides support for Quarkus development via a Quarkus language server and a Quarkus jdt.ls extension.
icon: https://www.eclipse.org/che/images/logo-eclipseche.svg
repository: https://github.com/redhat-developer/vscode-quarkus
category: Language
firstPublicationDate: "2019-11-05"
spec:
  containers:
    - image: "docker.io/eclipse/che-remote-plugin-runner-java11:next"
      name: vscode-quarkus
      memoryLimit: "1500Mi"
      volumes:
      - mountPath: "/home/theia/.m2"
        name: m2
  extensions:
    - https://github.com/microsoft/vscode-java-debug/releases/download/0.20.0/vscode-java-debug-0.20.0.vsix
    - https://download.jboss.org/jbosstools/static/jdt.ls/stable/java-0.50.0-1825.vsix
    - https://download.jboss.org/jbosstools/vscode/snapshots/vscode-quarkus/vscode-quarkus-1.1.1-158.vsix

About this issue

  • Original URL
  • State: open
  • Created 5 years ago
  • Comments: 30 (28 by maintainers)

Most upvoted comments

Any news on this? The problem still persists, it seems.

@amisevsk quarkus:dev is task’s name, the command is mvn quarkus:dev. Into debug configuration we have to put the name.