Markus KARG
Markus KARG
@sysmat Does that answer your question?
@sysmat As you were not responding, I assume that your answer was resolved. Hence I am closing this issue.
We cannot see the actual cause of this inside of JCommander. In fact, it is bash itself which is in your way. Bash is parsing the command line, and passes...
@priand As you did not respond to the last comment I assume my claim was correct, so I am closing this ticket now.
@marekkrk Can you please check your claim using the *latest* source code? There is a test that proofs both cases are working fine, see https://github.com/cbeust/jcommander/blob/master/src/test/java/com/beust/jcommander/JCommanderTest.java#L246-L247.
@marekkrk As you did not respond to the open question, I assume my claim was correct and this is no longer an issue. So I am closing this ticket now.
The reason simply is that the latest published jCommander is 1.82, which does not contain that feature. @cbeust I'd like to propose publishing jCommander 1.83 in Q1/2023, WDYT?
Closing this issue, as JCommander was published on Maven Central in 2024 (see https://repo1.maven.org/maven2/org/jcommander/jcommander/1.83/).
This sounds like a useful addition, but regarding your original use case I wonder if the route really is the template. Isn't it the actual resource?
> I'm not sure what you mean by "the actual resource" here. The concept of the "route" is defined by the OpenTelemetry Specification as the path template (in whatever format...