Jérémie Bresson
Jérémie Bresson
For example stuff added on the command line `--deps` / `--repos` is not present in the info tools JSON. --- But I think, ideally for me I would like this...
@quintesse: this is what I am doing: ``` ./jbang info tools myJBangScript ./jbang myJBangScript foo bar ``` `` is the same for the 2 runs. --- With `jbang info tools...
> What info is it you are missing specifically in the info tools ? The JBang version could be useful as well.
Probably it is more a bug than a feature. This is problematic: https://github.com/jbangdev/jbang/blob/ef362429c1c9a60aec8200b3f3184cbb74160c98/src/main/java/dev/jbang/source/ScriptSource.java#L158-L160 And the corresponding test: https://github.com/jbangdev/jbang/blob/ef362429c1c9a60aec8200b3f3184cbb74160c98/src/test/java/dev/jbang/source/TestScript.java#L265-L273 The `,` inside a range `[1.0.0, 1.1.0)` should be ignored when it...
Workaround: ```java ///usr/bin/env jbang "$0" "$@" ; exit $? //DEPS org.apache.groovy:groovy:4.0.0 import static java.lang.System.out; import org.apache.log4j.Logger; import org.apache.log4j.BasicConfigurator; import java.util.Arrays; import groovy.lang.Grab; import groovy.lang.Grapes; import groovy.lang.GrabResolver; @GrabResolver("mavenCentral") @Grapes({ @Grab(group="ch.qos.reload4j", module="reload4j",...
As reaction @maxandersen https://github.com/jbangdev/jbang/pull/1271#issuecomment-1110845388 and @quintesse https://github.com/jbangdev/jbang/pull/1271#issuecomment-1110848139 Currently `@Grab` is the only way I found to be able to define version range. If `,` is a valid separator for ```...
I think there is a some misunderstanding here. Rest-Assured works at HTTP level. It calls your application endpoint, potentially in a separated JVM process (if you run the tests from...
This makes sense... I wanted to add a sentence in [29.1. Defining an Anchor](http://asciidoctor.org/docs/user-manual/#anchordef). In the HTML backend case, just dropping the complete line without any error is not really...
> I think it just leaves it unparsed, doesn't it? Ok this is true. I had something else in mind. The image bloc is broken and therefore the xref links...
Thank you for your feedback. Maybe a first step is to have the possibility to apply a diff result on a specification. Take `spec1` and `spec2`: with the `ChangedOpenApi` object...