-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
quarkus:dev's debugHost not configurable #14403
Comments
You should be able to do |
I added a documentation note about that at #14421 |
Yep, that is what I already tried. I am not an expert for maven plugins, but the last time I wrote one, you needed to set a property (name) for your injected |
Thats the line, sorry for not linking it. You can configure this line using the plugin's |
That should also work |
Please run
Using quarkus 1.10.5.Final |
Add note about enabling all debug hosts for dev mode
Reopening as the OP says it doesn't help AFAICS. |
I'll have another look later
…On Wed, Jan 20, 2021, 13:35 Guillaume Smet ***@***.***> wrote:
Reopening as the OP says it doesn't help AFAICS.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#14403 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBMDP5YAKIY6TTM6AICONTS225XXANCNFSM4WI6LNEA>
.
|
#14432 fixes the issue |
Ensure that dev mode debug host can be configured with -DdebugHost
We are running development environments and tools in containers and trying to separate responsibilities not only in separate containers (and also pods, so colocation is not really a solution). One of the ideas was separate IDE pods from the actual application (quarkus-based, in this occasion) being in development. The challenge for us is, to make relevant ports from the application in development available at least to the IDE container.
When running
mvn quarkus:dev
, application's port is only bound to loopback interface, which is luckily configurable e.g. via enviroment variableQUARKUS_HTTP_HOST=0.0.0.0
. The same problem applies to other ports like the debug port, which is opened by the maven plugin. Unfortunately it looks like there is currently no way to change this configuration, even though most of the code to do so is already there (have a look atio.quarkus.maven.DevMojo#debugHost
).Expected behavior
When running
mvn quarkus:dev
debug port is bound to 127.0.0.1 by default, but is configurable somehow.Actual behavior
Running
mvn quarkus:dev
debug port is bound to 127.0.0.1 and not configurable.To Reproduce
Without containering: Start any quarkus application using
mvn quarkus:dev
and from the same machine try to connect to it usingjdb -attach $(hostname):5005
.jdb -attach localhost:5005
is working fine for reference.The text was updated successfully, but these errors were encountered: