-
Notifications
You must be signed in to change notification settings - Fork 10
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
Maven Run Configuration on Windows with WSL does not start mirrord #149
Comments
I've had no luck with this so far. Trying to run the quarkus "RestEasy" project (created from Intellij Ultimate) with mirrord, just resulted in Intellij spinning things and progress bars going for around 1 hour (in wsl). It tries starting mirrord, but we never get anywhere. Still investigating what could be going on here. |
Reproduces on linux as well. The quarkus sample starts, but no sign of mirrord, no sign of agent either. |
Looks like we don't hook the correct extension point for quarkus. It uses the
Even though quarkus comes with Intellij Ultimate, I can't seem to import Would appreciate if anyone more familiar with the Intellij SDK and how mirrord-intellij starts could throw some ideas around. |
We've tried extending the quarkus plugin to get access to the command line, but there is no public API there, everything is Aviram opened an issue in the intellij tracker asking for the stuff we need ( Current issue is blocked until we get some feedback. |
Bug Description
I have a Quarkus 3.2.3.final project that is using Maven 3.9.4. The Run Configuration is of type "Maven" with the goal "quarkus:dev" with an Ubuntu 20.04 running with WSL as run target. I'm using Intellij Ultimate 2023.2.1
When i try to execute that Run Configuration, mirrord seems to be doing nothing at all. I receive no error, log output or pop-up from mirrord.
Steps to Reproduce
Backtrace
No response
Relevant Logs
No response
Your operating system and version
Windows 10 22H2, WSL with Ubuntu 20.04, Plugin Version 3.54.3
Local process
"Maven" Run Configuration
Local process version
No response
Additional Info
No response
The text was updated successfully, but these errors were encountered: