-
Notifications
You must be signed in to change notification settings - Fork 15
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
CodeLens URL does not respect quarkus.http.root-path property #368
Comments
As an alternative to properties support extension, it is also possible to add support for |
Sorry @clochardpagan I see your issue now. I didn't know this property
Indeed the check which is done to show/hide CodeLens is done here https://github.com/eclipse/lsp4mp/blob/ab86a54e2be98c20ada1664ce910a015779c6b4d/microprofile.jdt/org.eclipse.lsp4mp.jdt.core/src/main/java/org/eclipse/lsp4mp/jdt/internal/jaxrs/java/JaxRsCodeLensParticipant.java#L99 It's very basic: check if we can connect a Socket to the localhost on a given port. The question is how to know the host (which config can we use)?
Same question, how to generate URL with https (which config can we use?)
Indeed we should manage this annotation too. |
As a minor quibble, if you auto-complete the
Might be nice to add an easy validation if it isn't too much effort, as the error stacktrace can make it difficult to get to the exact root cause. |
@clochardpagan could you give us how to you can configure the host in quarkus application please?
@clochardpagan how do you enable SSL? Do you use quarkus ssl property https://quarkus.io/guides/http-reference#providing-a-certificate-and-key-file ? If it that it means that we could generate https when we find in the application.properties a quarkus ssl property. |
If we set
quarkus.http.root-path
to point at/some/special/place/in/your/heart
, and try to fire up VS Code, lens will be generated with default hosthttp://localhost:8080/{some-place-specified-with-@Path-annotaion}
.There was a pull request by @angelozerr which added support for port change - thanks, mate. @fbricon merged it on 27th of January. But... we have two more problems:
localhost
. That's a problem.https://
at all. Bad, but can be fixed via SSL termination or/and proxy.The text was updated successfully, but these errors were encountered: