A question:
is --camel-version supposed to allow a route to run with the older camel
version?
4.4.1 does work. Trying to identify if I should be able to run a previous
version.
I am on windows10
C:\work\jb>camel --version
4.4.1
C:\work\jb>jbang version
0.103.1
C:\work\jb>camel run b.java --verbose --camel-version=4.0.1
[jbang] Resolving dependencies...
[jbang] org.apache.camel:camel-bom:4.4.1@pom
[jbang] org.apache.camel:camel-jbang-core:4.4.1
[jbang] org.apache.camel.kamelets:camel-kamelets:4.4.0
[jbang] Dependencies resolved
[jbang] Building jar...
java.io.IOException: Cannot run program "jbang": CreateProcess error=2, The
system cannot find the file specified
at
java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1143)
at
java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1073)
at
org.apache.camel.dsl.jbang.core.commands.Run.runCamelVersion(Run.java:958)
at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:784)
at org.apache.camel.dsl.jbang.core.commands.Run.doCall(Run.java:298)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
at
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
at picocli.CommandLine.executeUserObject(CommandLine.java:2041)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2453)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2415)
at
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2417)
at picocli.CommandLine.execute(CommandLine.java:2170)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:159)
at
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:58)
at main.CamelJBang.main(CamelJBang.java:36)
Caused by: java.io.IOException: CreateProcess error=2, The system cannot
find the file specified
at java.base/java.lang.ProcessImpl.create(Native Method)
at java.base/java.lang.ProcessImpl.<init>(ProcessImpl.java:500)
at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:159)
at
java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110)
... 17 more
ચિરાગ/चिराग/Chirag
------------------------------------------
Sent from My Gmail Account
On Fri, Mar 22, 2024 at 2:55 AM Mikael Koskinen <mijap...@gmail.com> wrote:
> Thank you for the quick help! 4.4.1 now installed nicely.
>
> And thank you for the tip regarding how to install a specific app version
> using Jbang.
>
> Best regards,
> Mikael
>
> pe 22. maalisk. 2024 klo 7.30 Tadayoshi Sato (sato.tadayo...@gmail.com)
> kirjoitti:
>
> > 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
> >
>
