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

Camel Quarkus project not recognized right away as a Quarkus one #740

Closed
apupier opened this issue May 15, 2024 · 6 comments
Closed

Camel Quarkus project not recognized right away as a Quarkus one #740

apupier opened this issue May 15, 2024 · 6 comments

Comments

@apupier
Copy link
Member

apupier commented May 15, 2024

steps to reproduce:

  1. install VS Code Language support for Apache Camel (and VS Code Quarkus of course)
  2. open a folder for the VS Code instance
  3. Call command: Create a Camel Route with Yaml DSL (with name demo for instance)
  4. Call command: Create a Camel Quarkus project
  5. Call command: Debug Quarkus

--> There is a notification message mentioning that there is no Quarkus project found

Workarounds:

  • Call command Reload Window , then you can call command: Debug Quarkus
  • or create a dummy Java file
@fbricon
Copy link
Collaborator

fbricon commented May 15, 2024

looks like "Debug Quarkus" is not coming from our extension (it should be prefixed with "Quarkus:")
Screenshot 2024-05-15 at 14 53 37

@fbricon
Copy link
Collaborator

fbricon commented May 15, 2024

nope, that's us :-)

"title": "Debug Quarkus",

@fbricon
Copy link
Collaborator

fbricon commented May 15, 2024

I can't reproduce the problem following the instructions. ./mvnw quarkus:dev is executed

@apupier
Copy link
Member Author

apupier commented May 15, 2024

I cannot anymore neither...

@lordrip do you still reproduce? Do you see something in the steps to reproduce that is missing?

@lordrip
Copy link

lordrip commented May 20, 2024

@apupier those were the reproduction steps, but after reproducing it constantly 4 times during a call, now I cannot reproduce it anymore, I'll stay tuned if it happens again. Thanks for checking this out @fbricon

@apupier
Copy link
Member Author

apupier commented May 21, 2024

closing until we find how to reproduce again or have more information

@apupier apupier closed this as completed May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants