Ah Claus already did it. Thanks Claus :-) On Fri, Mar 22, 2024 at 2:29 PM Tadayoshi Sato <sato.tadayo...@gmail.com> wrote:
> Hi, > > The Camel JBang command looks at this file in the default branch. > > https://github.com/apache/camel/blob/main/dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java#L22-L24 > > As you see, it still points to 4.4.0. Someone will soon update it to 4.4.1 > and you should be able to use it. > > By the way, the latest JBang version allows us to pass additional system > properties at `jbang app install`, so you can as well now do this to > install a specific version of Camel JBang command: > > $ jbang app install -Dcamel.jbang.version=4.4.1 camel@apache/camel > > Hope it helps, > > On Fri, Mar 22, 2024 at 2:10 PM Mikael Koskinen <mijap...@gmail.com> > wrote: > >> Hi, >> >> I'm trying to install Camel Jbang 4.4.1 but the 4.4.0 always gets >> installed. --Force and --fresh parameters don't help. >> >> jbang app install --force --fresh camel@apache/camel >> >> I checked the CamelJBang.java and it still seems to refer to 4.4.0, is >> this >> something that needs to be changed on the source code side? >> >> I'm not actually that familiar with how the versioning with the Camel >> Jbang >> works. I assumed that the release of Camel 4.4.1 means that the Camel >> Jbang >> is also updated to the same version. But now I noticed that there's no >> 4.4.1 release for the docker image either, so I assume they have a >> different release cadence. >> >> Specifying the exact version when running a command works, for example: >> >> jbang --fresh "-Dcamel.jbang.version=4.4.1" camel@apache/camel --version >> >> Best regards, >> Mikael >> > > > -- > Tadayoshi Sato > -- Tadayoshi Sato
