-
Notifications
You must be signed in to change notification settings - Fork 9
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
fix: make proxy a runnable jar from maven #125
Conversation
maxandersen
commented
Feb 25, 2025
- make the released proxy jar directly runnable
- remove unneeded --quiet
- document runnable jar coordinates (works when this is released)
devtools/stdio-sse-proxy/src/main/java/io/quarkiverse/mcp/server/proxy/StdioSseProxy.java
Outdated
Show resolved
Hide resolved
|
||
```shell script | ||
jbang io.quarkiverse.mcp:quarkus-mcp-stdio-sse-proxy:RELEASE -h |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does the :RELEASE
stand for? Is it handled specifically by JBang?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
standard maven coordinate syntax for getting latest released version (non-snapshot)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it? I've never heard about it. I mean, io.quarkiverse.mcp:quarkus-mcp-stdio-sse-proxy:RELEASE
is not a valid Maven artifact coordinate (at least according to chatgpt and https://maven.apache.org/guides/mini/guide-naming-conventions.html). release
is a valid qualifier but nothing more. But maybe I'm missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its been around since Maven 2 - see https://stackoverflow.com/questions/30571/how-do-i-tell-maven-to-use-the-latest-version-of-a-dependency/1172371#1172371
it is not jbang doing any interpretation here - its maven resolver and you can use <version>RELEASE</version>
in your pom.xml dependencies (but not for plugins).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. The RELEASE and LATEST markers seem to be a deprecated legacy feature from Maven 2 ;-). At least, I wasn't able to find any official docs, except for https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=2852668#Maven3.xCompatibilityNotes-PluginMetaversionResolution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is for plugins it was explicitly removed as makes builds irreproducible. still possible for resolver because it is useful - like in cases like this.
its like docker pull xyz:latest
or sdk install quarkus
where you just get the latest.
81e00eb
to
4a8e7ae
Compare