Hey,

I was now able to test things using the latest 3.20.0-SNAPSHOT in
Windows 10 but unfortunately the issue seems to persist.

I started from a new clean folder and then issued:

jbang run --fresh "-Dcamel.jbang.version=3.20.0-SNAPSHOT"
camel@apache/camel export --runtime=
quarkus --gav=com.foo:acme:1.0-SNAPSHOT -dir=pub --quarkus-version=2.14.2.Final

There's couple new dependencies, but unfortunately the pom.xml still
isn't using quarkus everywhere:

---

    <dependencies>
        <dependency>
            <groupId>org.apache.camel.quarkus</groupId>
            <artifactId>camel-quarkus-core</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.camel.quarkus</groupId>
            <artifactId>camel-quarkus-platform-http</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.camel.quarkus</groupId>
            <artifactId>camel-quarkus-microprofile-health</artifactId>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-file-watch</artifactId>
            <version>3.20.0-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-http</artifactId>
            <version>3.20.0-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-kamelet</artifactId>
            <version>3.20.0-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-rest</artifactId>
            <version>3.20.0-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel</groupId>
            <artifactId>camel-yaml-dsl</artifactId>
            <version>3.20.0-SNAPSHOT</version>
        </dependency>
        <dependency>
            <groupId>org.apache.camel.kamelets</groupId>
            <artifactId>camel-kamelets-utils</artifactId>
            <version>0.9.3</version>
            <exclusions>
                <exclusion>
                    <groupId>org.apache.camel</groupId>
                    <artifactId>*</artifactId>
                </exclusion>
            </exclusions>
        </dependency>
        <dependency>
            <groupId>org.apache.camel.kamelets</groupId>
            <artifactId>camel-kamelets</artifactId>
            <version>0.9.3</version>
        </dependency>


        <dependency>
            <groupId>io.quarkus</groupId>
            <artifactId>quarkus-junit5</artifactId>
            <scope>test</scope>
        </dependency>
    </dependencies>

---

Diffing this vs the previous version I see that these are new
dependencies which weren't added previously:

camel-kamelet
camel-kamelets-utils
camel-kamelets

When I previously manually modified the pom.xml to make things work I
had to add the following two which aren't included in the newly
generated pom.xml:

camel-quarkus-kamelet
camel-kamelets-catalog

I'm not sure what's the difference between camel-kamelets and
camel-kamelets-catalog.

ke 30. marrask. 2022 klo 20.21 Mikael Koskinen (mijap...@gmail.com) kirjoitti:
>
> Hi,
>
> Thanks! I'll try the SNAPSHOT tomorrow and report back on how it works.
>
> ke 30. marrask. 2022 klo 15.05 Claus Ibsen (claus.ib...@gmail.com) kirjoitti:
> >
> > Hi
> >
> > Okay I have a potential fix.
> >
> > You can test this by building from source (or wait till tomorrow for CI
> > server to publish a new SNAPSHOT)
> > For source you only need to build dsl/camel-jbang
> >
> > So checkout the camel source code ( a lot of source )
> > cd dsl/camel-jbang
> > mvn clean install
> >
> > and then try again on windows
> >
> > On Wed, Nov 30, 2022 at 1:55 PM Claus Ibsen <claus.ib...@gmail.com> wrote:
> >
> > > Hi
> > >
> > > Yeah I think its a windows bug in camel-jbang, we had to download
> > > camel-quarkus-catalog in a special way with the Shrinkwrap project.
> > > However now we use standard Maven so we can likely downloader this in a
> > > better way that can work for windows too
> > > https://issues.apache.org/jira/browse/CAMEL-18778
> > >
> > > On Wed, Nov 30, 2022 at 1:48 PM Mikael Koskinen <mijap...@gmail.com>
> > > wrote:
> > >
> > >> Hey,
> > >>
> > >> I tested with Mac and it worked from the get go with 3.20.0-SNAPSHOT:
> > >> all the dependencies are quarkus versions as expected.
> > >>
> > >> Haven't been able to test the Spring boot & Windows combination yet.
> > >>
> > >> ke 30. marrask. 2022 klo 11.25 Mikael Koskinen (mijap...@gmail.com)
> > >> kirjoitti:
> > >> >
> > >> > Hi,
> > >> >
> > >> > Yep, using Windows. I’ll try the Spring boot export & running things
> > >> with Mac later today and report back with my findings.
> > >> >
> > >> > On Wednesday, November 30, 2022, Claus Ibsen <claus.ib...@gmail.com>
> > >> wrote:
> > >> >>
> > >> >> Hi
> > >> >>
> > >> >> Are you using windows btw? I suspect it may also be related to that,
> > >> as it
> > >> >> smells like the camel-quarkus-catalog (needed for export to Q)
> > >> >> is not downloaded and resolved correctly so we fallback to core camel
> > >> maven
> > >> >> GAVs
> > >> >>
> > >> >> Can you try to export to spring boot and look in the generated pom.xml
> > >> that
> > >> >> the GAVs are using camel-xxx-starter ?
> > >> >>
> > >> >>
> > >> >>
> > >> >>
> > >> >> On Tue, Nov 29, 2022 at 8:12 PM Mikael Koskinen <mijap...@gmail.com>
> > >> wrote:
> > >> >>
> > >> >> > Hey,
> > >> >> >
> > >> >> > Thank you for the help here and in the Gist.
> > >> >> >
> > >> >> > Based on the suggestions I tested the JBang version 3.20.0-SNAPSHOT
> > >> >> > and with Quarkus 2.14.2.Final and still encountered the same issue.
> > >> >> >
> > >> >> > Manually modifying the exported pom.xml got things working. I 
> > >> >> > updated
> > >> >> > the gist with logs and also with the changes I did to pom.xml to 
> > >> >> > make
> > >> >> > things work.
> > >> >> >
> > >> >> > ti 29. marrask. 2022 klo 8.21 Claus Ibsen (claus.ib...@gmail.com)
> > >> >> > kirjoitti:
> > >> >> > >
> > >> >> > > Hi
> > >> >> > >
> > >> >> > > I created a ticket at CEQ
> > >> >> > > https://github.com/apache/camel-quarkus/issues/4300
> > >> >> > >
> > >> >> > > What camel-quarkus version are you using btw. You can try with
> > >> latest
> > >> >> > > 2.14.2 release, you can re-export and set the quarkus version with
> > >> the
> > >> >> > > --quarkus-version option, or adjust the existing pom.xml
> > >> >> > >
> > >> >> > > On Tue, Nov 29, 2022 at 7:10 AM Claus Ibsen <claus.ib...@gmail.com
> > >> >
> > >> >> > wrote:
> > >> >> > >
> > >> >> > > > Hi
> > >> >> > > >
> > >> >> > > > Yeah it suspect quarkus http extension does not bring in servlet
> > >> api
> > >> >> > JAR
> > >> >> > > > which is needed by camel-http.
> > >> >> > > >
> > >> >> >
> > >> https://github.com/apache/camel/blob/main/components/camel-http/pom.xml#L55
> > >> >> > > >
> > >> >> > > > You can when doing export try adding
> > >> >> > > > --deps=javax.servlet:javax.servlet-api:3.1.0 (or whatever maven
> > >> JAR
> > >> >> > that
> > >> >> > > > quarkus uses for servlet as there are many of them)
> > >> >> > > >
> > >> >> > > > On Fri, Nov 25, 2022 at 8:30 PM Mikael Koskinen <
> > >> mijap...@gmail.com>
> > >> >> > > > wrote:
> > >> >> > > >
> > >> >> > > >> Hi,
> > >> >> > > >>
> > >> >> > > >> I have some issues when trying to export an integration to
> > >> Quarkus
> > >> >> > > >> runtime using Camel JBang if the integration uses
> > >> >> > > >> kamelet:http-sink.The sample integration causing issues is
> > >> available
> > >> >> > > >> from here:
> > >> >> > > >>
> > >> https://gist.github.com/mikoskinen/71ce1d1ba5b5d7b690a4ec12af20e8ec
> > >> >> > > >>
> > >> >> > > >> The integration runs fine using "camel run myintegration.yaml"
> > >> >> > > >>
> > >> >> > > >> But if I export it to Quarkus using "camel export -dir=pub
> > >> >> > > >> --gav=com.foo:acme:1.0-SNAPSHOT --runtime=quarkus --fresh"
> > >> >> > > >>
> > >> >> > > >> And then try to run things using "mvn compile quarkus:dev" I
> > >> get:
> > >> >> > > >>
> > >> >> > > >> ERROR [io.qua.run.boo.StartupActionImpl] (Quarkus Main Thread)
> > >> Error
> > >> >> > > >> running Quarkus: java.lang.reflect.InvocationTargetException
> > >> >> > > >> ...
> > >> >> > > >> Caused by: java.lang.ClassNotFoundException:
> > >> >> > > >> javax.servlet.http.HttpServletRequest
> > >> >> > > >> at
> > >> >> > > >>
> > >> >> >
> > >> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> > >> >> > > >> at
> > >> >> > > >>
> > >> >> >
> > >> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> > >> >> > > >> at
> > >> java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
> > >> >> > > >> at
> > >> >> > > >>
> > >> >> >
> > >> io.quarkus.bootstrap.classloading.QuarkusClassLoader.loadClass(QuarkusClassLoader.java:490)
> > >> >> > > >> at
> > >> >> > > >>
> > >> >> >
> > >> io.quarkus.bootstrap.classloading.QuarkusClassLoader.loadClass(QuarkusClassLoader.java:440)
> > >> >> > > >>
> > >> >> > > >> The full exception is available from the same gist:
> > >> >> > > >>
> > >> https://gist.github.com/mikoskinen/71ce1d1ba5b5d7b690a4ec12af20e8ec
> > >> >> > > >>
> > >> >> > > >> If I export to Camel Main it works OK.
> > >> >> > > >>
> > >> >> > > >> Am I missing something? Any advice is appreciated.
> > >> >> > > >>
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > --
> > >> >> > > > Claus Ibsen
> > >> >> > > > -----------------
> > >> >> > > > @davsclaus
> > >> >> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > >> >> > > >
> > >> >> > >
> > >> >> > >
> > >> >> > > --
> > >> >> > > Claus Ibsen
> > >> >> > > -----------------
> > >> >> > > @davsclaus
> > >> >> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >> >> >
> > >> >>
> > >> >>
> > >> >> --
> > >> >> Claus Ibsen
> > >> >> -----------------
> > >> >> @davsclaus
> > >> >> Camel in Action 2: https://www.manning.com/ibsen2
> > >>
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to