[jira] [Commented] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
[
https://issues.apache.org/jira/browse/CAMEL-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864167#comment-17864167
]
Grzegorz Grzybek commented on CAMEL-20948:
--
Actually the same fix is in the original library:
https://github.com/cliftonlabs/json-simple/commit/cbdd1fa3efd0af25671f29f877dcf70c76dfc4e4
> camel-util-json doesn't handle streaming correctly
> --
>
> Key: CAMEL-20948
> URL: https://issues.apache.org/jira/browse/CAMEL-20948
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 4.7.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.7.0
>
>
> I was checking Jolokia with different JSON libraries:
> * https://github.com/jolokia/jolokia/issues/686
> * https://github.com/jolokia/jolokia/issues/252
> and I decided to check [~davsclaus]
> [suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
> I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
> libraries. I have 10K queues (which means 20K MBeans for the queues alone)
> and I check Jolokia {{list()}} operation. Initially I got:
> {noformat}
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
> ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
> ~[?:?]
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
> at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
> ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
> ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
> ~[?:?]
> at
> org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
> ~[jetty-servlet-11.0.18.jar:11.0.18]
> ...
> {noformat}
> but I quickly realized there's a problem about String / Writer handling in
> camel-util-json. PR pending.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
[
https://issues.apache.org/jira/browse/CAMEL-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-20948.
--
Resolution: Fixed
> camel-util-json doesn't handle streaming correctly
> --
>
> Key: CAMEL-20948
> URL: https://issues.apache.org/jira/browse/CAMEL-20948
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 4.7.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.7.0
>
>
> I was checking Jolokia with different JSON libraries:
> * https://github.com/jolokia/jolokia/issues/686
> * https://github.com/jolokia/jolokia/issues/252
> and I decided to check [~davsclaus]
> [suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
> I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
> libraries. I have 10K queues (which means 20K MBeans for the queues alone)
> and I check Jolokia {{list()}} operation. Initially I got:
> {noformat}
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
> ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
> ~[?:?]
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
> at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
> ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
> ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
> ~[?:?]
> at
> org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
> ~[jetty-servlet-11.0.18.jar:11.0.18]
> ...
> {noformat}
> but I quickly realized there's a problem about String / Writer handling in
> camel-util-json. PR pending.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
[
https://issues.apache.org/jira/browse/CAMEL-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-20948:
-
Fix Version/s: 4.7.0
(was: 4.8.0)
> camel-util-json doesn't handle streaming correctly
> --
>
> Key: CAMEL-20948
> URL: https://issues.apache.org/jira/browse/CAMEL-20948
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Affects Versions: 4.7.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.7.0
>
>
> I was checking Jolokia with different JSON libraries:
> * https://github.com/jolokia/jolokia/issues/686
> * https://github.com/jolokia/jolokia/issues/252
> and I decided to check [~davsclaus]
> [suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
> I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
> libraries. I have 10K queues (which means 20K MBeans for the queues alone)
> and I check Jolokia {{list()}} operation. Initially I got:
> {noformat}
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
> ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
> ~[?:?]
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
> at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
> ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
> ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
> ~[?:?]
> at
> org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
> ~[jetty-servlet-11.0.18.jar:11.0.18]
> ...
> {noformat}
> but I quickly realized there's a problem about String / Writer handling in
> camel-util-json. PR pending.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
[
https://issues.apache.org/jira/browse/CAMEL-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863356#comment-17863356
]
Grzegorz Grzybek commented on CAMEL-20948:
--
PR: https://github.com/apache/camel/pull/14747
> camel-util-json doesn't handle streaming correctly
> --
>
> Key: CAMEL-20948
> URL: https://issues.apache.org/jira/browse/CAMEL-20948
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.7.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I was checking Jolokia with different JSON libraries:
> * https://github.com/jolokia/jolokia/issues/686
> * https://github.com/jolokia/jolokia/issues/252
> and I decided to check [~davsclaus]
> [suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
> I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
> libraries. I have 10K queues (which means 20K MBeans for the queues alone)
> and I check Jolokia {{list()}} operation. Initially I got:
> {noformat}
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
> ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
> ~[?:?]
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
> at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
> ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
> ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
> ~[?:?]
> at
> org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
> ~[jakarta.servlet-api-5.0.0.jar:5.0.0]
> at
> org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
> ~[jetty-servlet-11.0.18.jar:11.0.18]
> ...
> {noformat}
> but I quickly realized there's a problem about String / Writer handling in
> camel-util-json. PR pending.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
[
https://issues.apache.org/jira/browse/CAMEL-20948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-20948:
-
Description:
I was checking Jolokia with different JSON libraries:
* https://github.com/jolokia/jolokia/issues/686
* https://github.com/jolokia/jolokia/issues/252
and I decided to check [~davsclaus]
[suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
libraries. I have 10K queues (which means 20K MBeans for the queues alone) and
I check Jolokia {{list()}} operation. Initially I got:
{noformat}
java.lang.OutOfMemoryError: Java heap space
at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
at
java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
~[?:?]
at
java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
~[?:?]
at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
~[?:?]
at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
~[?:?]
at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
~[?:?]
at
org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
~[?:?]
at
org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
~[?:?]
at
org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
~[?:?]
at
org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
at
org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:520)
~[jakarta.servlet-api-5.0.0.jar:5.0.0]
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:587)
~[jakarta.servlet-api-5.0.0.jar:5.0.0]
at
org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1419)
~[jetty-servlet-11.0.18.jar:11.0.18]
...
{noformat}
but I quickly realized there's a problem about String / Writer handling in
camel-util-json. PR pending.
> camel-util-json doesn't handle streaming correctly
> --
>
> Key: CAMEL-20948
> URL: https://issues.apache.org/jira/browse/CAMEL-20948
> Project: Camel
> Issue Type: Bug
> Components: tooling
>Affects Versions: 4.7.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
>
> I was checking Jolokia with different JSON libraries:
> * https://github.com/jolokia/jolokia/issues/686
> * https://github.com/jolokia/jolokia/issues/252
> and I decided to check [~davsclaus]
> [suggestion|https://github.com/jolokia/jolokia/issues/686#issuecomment-2151669446].
> I am using Artemis instance with Hawtio 4, Jolokia 2 and different JSON
> libraries. I have 10K queues (which means 20K MBeans for the queues alone)
> and I check Jolokia {{list()}} operation. Initially I got:
> {noformat}
> java.lang.OutOfMemoryError: Java heap space
> at java.base/java.util.Arrays.copyOf(Arrays.java:3537) ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:228)
> ~[?:?]
> at
> java.base/java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:802)
> ~[?:?]
> at java.base/java.lang.StringBuffer.append(StringBuffer.java:425) ~[?:?]
> at java.base/java.io.StringWriter.write(StringWriter.java:77) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:768)
> ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:747)
> ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:946) ~[?:?]
> at org.apache.camel.util.json.Jsoner.serialize(Jsoner.java:924) ~[?:?]
> at org.apache.camel.util.json.JsonObject.toJson(JsonObject.java:773)
> ~[?:?]
> at
> org.jolokia.server.core.util.IoUtil.streamResponseAndClose(IoUtil.java:33)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendStreamingResponse(AgentServlet.java:575)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.sendResponse(AgentServlet.java:558)
> ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.handle(AgentServlet.java:359) ~[?:?]
> at
> org.jolokia.server.core.http.AgentServlet.doPost(AgentServlet.java:298) ~[?:?]
> at
[jira] [Created] (CAMEL-20948) camel-util-json doesn't handle streaming correctly
Grzegorz Grzybek created CAMEL-20948: Summary: camel-util-json doesn't handle streaming correctly Key: CAMEL-20948 URL: https://issues.apache.org/jira/browse/CAMEL-20948 Project: Camel Issue Type: Bug Components: tooling Affects Versions: 4.7.0 Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20847) camel-jbang - Run with jolokia enabled does not work
[
https://issues.apache.org/jira/browse/CAMEL-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853035#comment-17853035
]
Grzegorz Grzybek commented on CAMEL-20847:
--
ok - so I recommend switching to non-classifier version (you'll get proper
classpath) and use javaagent flavor ONLY as part of some assembly methods (like
packaging jbang applications, with maven-assembly-plugin, ...). {{javaagent}}
classifier flavor should NOT be used as Maven dependency.
> camel-jbang - Run with jolokia enabled does not work
>
>
> Key: CAMEL-20847
> URL: https://issues.apache.org/jira/browse/CAMEL-20847
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.6.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: Screenshot 2024-06-06 at 16.12.21.png
>
>
> 2024-06-06 15:59:35.592 ERROR 78029 --- [ntloop-thread-0]
> io.vertx.ext.web.RoutingContext : Unhandled exception in router
> java.lang.NoSuchMethodError: 'org.json.simple.JSONObject
> org.jolokia.server.core.http.HttpRequestHandler.handleThrowable(java.lang.Throwable)'
> at
> org.apache.camel.component.platform.http.plugin.DefaultJolokiaPlatformHttpPlugin.lambda$createVertxHandler$0(DefaultJolokiaPlatformHttpPlugin.java:184)
> ~[camel-platform-http-jolokia-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT]
> at
> io.vertx.ext.web.impl.BlockingHandlerDecorator.lambda$handle$0(BlockingHandlerDecorator.java:48)
> ~[vertx-web-4.5.7.jar:4.5.7]
> at
> io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:191)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:279)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at
> io.vertx.core.impl.ContextImpl.lambda$internalExecuteBlocking$2(ContextImpl.java:210)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [netty-common-4.1.108.Final.jar:4.1.108.Final]
> at java.base/java.lang.Thread.run(Thread.java:833) [?:?]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20847) camel-jbang - Run with jolokia enabled does not work
[
https://issues.apache.org/jira/browse/CAMEL-20847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853024#comment-17853024
]
Grzegorz Grzybek commented on CAMEL-20847:
--
The screenshot shows {{org.jolokia.shaded.org.json.simple.xxx}} references. But
this shaded class is ONLY included in one specific artifact:
{code:xml}
org.jolokia
jolokia-agent-jvm
jolokia-server-core
${jolokia-version}
javaagent
{code}
This is explained in
https://jolokia.org/migration.html#jolokia_jvm_agent_module.
Plain {{org.jolokia:jolokia-agent-jvm:jar:2.0.3:compile}} dependency (no
classifier) simply depends on
{{com.googlecode.json-simple:json-simple:jar:1.1.1:compile}} instead of shading
it. Are you sure your classpath doesn't contain the {{javaagent}} version?
> camel-jbang - Run with jolokia enabled does not work
>
>
> Key: CAMEL-20847
> URL: https://issues.apache.org/jira/browse/CAMEL-20847
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.6.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
> Attachments: Screenshot 2024-06-06 at 16.12.21.png
>
>
> 2024-06-06 15:59:35.592 ERROR 78029 --- [ntloop-thread-0]
> io.vertx.ext.web.RoutingContext : Unhandled exception in router
> java.lang.NoSuchMethodError: 'org.json.simple.JSONObject
> org.jolokia.server.core.http.HttpRequestHandler.handleThrowable(java.lang.Throwable)'
> at
> org.apache.camel.component.platform.http.plugin.DefaultJolokiaPlatformHttpPlugin.lambda$createVertxHandler$0(DefaultJolokiaPlatformHttpPlugin.java:184)
> ~[camel-platform-http-jolokia-4.7.0-SNAPSHOT.jar:4.7.0-SNAPSHOT]
> at
> io.vertx.ext.web.impl.BlockingHandlerDecorator.lambda$handle$0(BlockingHandlerDecorator.java:48)
> ~[vertx-web-4.5.7.jar:4.5.7]
> at
> io.vertx.core.impl.ContextImpl.lambda$executeBlocking$1(ContextImpl.java:191)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:279)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at
> io.vertx.core.impl.ContextImpl.lambda$internalExecuteBlocking$2(ContextImpl.java:210)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76)
> ~[vertx-core-4.5.7.jar:4.5.7]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> [netty-common-4.1.108.Final.jar:4.1.108.Final]
> at java.base/java.lang.Thread.run(Thread.java:833) [?:?]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19846) camel-yaml-dsl: Support setting MessageHistoryFactory.setCopyMessage(true) from YAML DSL
[
https://issues.apache.org/jira/browse/CAMEL-19846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766731#comment-17766731
]
Grzegorz Grzybek commented on CAMEL-19846:
--
bq. both xml-io-dsl and yaml-dsl that creates bean, but does not support beans
that are for those rare advanced settings on camel context like that message
history factory
Actually with
https://github.com/apache/camel/blob/c51b052/dsl/camel-xml-io-dsl/src/main/java/org/apache/camel/dsl/xml/io/XmlRoutesBuilderLoader.java#L83-L102,
XML DSL can add beans to registry early enough, so they are visible in
https://github.com/apache/camel/blob/0165a54/core/camel-main/src/main/java/org/apache/camel/main/DefaultConfigurationConfigurer.java#L378
See example here:
https://github.com/apache/camel-kamelets-examples/blob/a6f59c2/jbang/app-routes-spring-beans/app.xml#L20-L22
I didn't check (super busy with Jolokia now) this new BeanLoader SPI yet...
> camel-yaml-dsl: Support setting MessageHistoryFactory.setCopyMessage(true)
> from YAML DSL
>
>
> Key: CAMEL-19846
> URL: https://issues.apache.org/jira/browse/CAMEL-19846
> Project: Camel
> Issue Type: Improvement
> Components: camel-yaml-dsl
>Affects Versions: 4.0.0
>Reporter: Tomohisa Igarashi
>Priority: Major
> Fix For: 4.1.0
>
>
> Support setting `MessageHistoryFactory.setCopyMessage(true)` from YAML DSL.
> I'm on a case to do it from YAML DSL, -but it seems other DSLs also don't yet
> directly support it other than providing a separate property file-. Turned
> out XML DSL already supports it with beans. For YAML DSL the beans
> registration is too late for comelContext configuration ATM. See comments.
> {code:yaml}
> - beans:
> - name: messageHistoryFactory
> type: org.apache.camel.impl.engine.DefaultMessageHistoryFactory
> properties:
> copyMessage: true
> - route:
> messageHistory: true
> from:
> uri: "timer:yaml"
> parameters:
> period: "3000"
> steps:
> - to:
> uri: "log:test"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751056#comment-17751056 ] Grzegorz Grzybek commented on CAMEL-19637: -- The solution from MRESOLVER-387 is nice, but we don't have to do it - we'd need additional dependency and also wait for maven-resolver-1.9.15 > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-19637. -- Resolution: Fixed Fixed here: https://github.com/apache/camel/commit/5960074805250b5239e034d9d892e97049920601 > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Fix Version/s: (was: 3.22.0) > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Fix Version/s: 3.22.0 > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.22.0, 4.0.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Fix Version/s: 4.0.0 (was: 4.1.0) > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19462) camel-package-maven-plugin - Make it Maven 4 compatible
[ https://issues.apache.org/jira/browse/CAMEL-19462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751022#comment-17751022 ] Grzegorz Grzybek commented on CAMEL-19462: -- Introducing plexus-xml 4.0.2 brought these Maven 4 transitive dependencies: * org.apache.maven/maven-api-meta * org.apache.maven/maven-api-xml * org.apache.maven/maven-xml-impl I thnk Camel itself should stay at Maven 3 (with CAMEL-19637 it'll be Maven 3.9.4 + Maven Resolver 1.9.14) > camel-package-maven-plugin - Make it Maven 4 compatible > --- > > Key: CAMEL-19462 > URL: https://issues.apache.org/jira/browse/CAMEL-19462 > Project: Camel > Issue Type: Task > Components: build system >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > [WARNING] * org.apache.camel:camel-package-maven-plugin:4.0.0-SNAPSHOT > [WARNING] Plugin issue(s): > [WARNING]* Plugin depends on the deprecated Maven 2.x compatibility > layer, which may not be supported in Maven 4.x > [WARNING]* Plugin depends on plexus-container-default, which is EOL -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Summary: camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 (was: camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14) > camel-tooling-maven - Upgrade to maven 3.9.4 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.1.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17747042#comment-17747042 ] Grzegorz Grzybek commented on CAMEL-19637: -- We may have much lighter way to configure the resolver soon: MRESOLVER-387 > camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.1.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Summary: camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14 (was: camel-tooling-maven - Upgrade to maven 3.9.3) > camel-tooling-maven - Upgrade to maven 3.9.3 and maven-resolver 1.9.14 > -- > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.1.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19637) camel-tooling-maven - Upgrade to maven 3.9.3
[ https://issues.apache.org/jira/browse/CAMEL-19637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19637: - Summary: camel-tooling-maven - Upgrade to maven 3.9.3 (was: camel-tooling-maven - Upgrade to maven resolver 3.9.3) > camel-tooling-maven - Upgrade to maven 3.9.3 > > > Key: CAMEL-19637 > URL: https://issues.apache.org/jira/browse/CAMEL-19637 > Project: Camel > Issue Type: Dependency upgrade > Components: tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.1.0 > > > We are using 3.8.8 and there is a 3.9.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19577) camel-jbang - Maven resolver logs verbose about downloading that we should get rid of
[ https://issues.apache.org/jira/browse/CAMEL-19577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740114#comment-17740114 ] Grzegorz Grzybek commented on CAMEL-19577: -- This is quite well known problem with the resolver - it tries to be helpful, but usually it is annoying. And yes - it's all about ID of the repo, which may be different in your settings.xml. with embedded usage it's even trickier. > camel-jbang - Maven resolver logs verbose about downloading that we should > get rid of > - > > Key: CAMEL-19577 > URL: https://issues.apache.org/jira/browse/CAMEL-19577 > Project: Camel > Issue Type: Task > Components: camel-jbang >Affects Versions: 3.21.0, 4.0-RC1 >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.21.1, 4.0.0 > > > 2023-07-05 10:31:43.296 INFO 9147 --- [- MavenDownload] > ternal.impl.DefaultArtifactResolver : Artifact > org.apache.camel:camel-tooling-model:pom:3.21.0 is present in the local > repository, but cached from a remote repository ID that is unavailable in > current build context, verifying that is downloadable from [central > (https://repo1.maven.org/maven2, default, releases)] > 2023-07-05 10:31:43.296 INFO 9147 --- [- MavenDownload] > ternal.impl.DefaultArtifactResolver : Artifact > org.apache.camel:camel-tooling-model:pom:3.21.0 is present in the local > repository, but cached from a remote repository ID that is unavailable in > current build context, verifying that is downloadable from [central > (https://repo1.maven.org/maven2, default, releases)] > 2023-07-05 10:31:43.334 INFO 9147 --- [- MavenDownload] > ternal.impl.DefaultArtifactResolver : Artifact > org.apache.camel:camel-tooling-model:jar:3.21.0 is present in the local > repository, but cached from a remote repository ID that is unavailable in > current build context, verifying that is downloadable from [central > (https://repo1.maven.org/maven2, default, releases)] > 2023-07-05 10:31:43.335 INFO 9147 --- [- MavenDownload] > ternal.impl.DefaultArtifactResolver : Artifact > org.apache.camel:camel-tooling-model:jar:3.21.0 is present in the local > repository, but cached from a remote repository ID that is unavailable in > current build context, verifying that is downloadable from [central > (https://repo1.maven.org/maven2, default, releases)] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19564) xml-io-dsl: Allow routes to use beans loaded directly from source
[
https://issues.apache.org/jira/browse/CAMEL-19564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-19564.
--
Resolution: Fixed
> xml-io-dsl: Allow routes to use beans loaded directly from source
> -
>
> Key: CAMEL-19564
> URL: https://issues.apache.org/jira/browse/CAMEL-19564
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.0.0
>
>
> With CAMEL-18189 we can now use {{}} elements in XMLs with top-level
> {{}} (or {{}}) elements.
> However it is not possible to load classes which come from {{*.java}} files
> passed to {{camel run}} because xml-io-dsl registers beans eagerly in
> {{org.apache.camel.spi.RoutesBuilderLoader#preParseRoute()}}.
> I have a PR which delays instantiation of such beans till when they're
> available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19564) xml-io-dsl: Allow routes to use beans loaded directly from source
[
https://issues.apache.org/jira/browse/CAMEL-19564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738991#comment-17738991
]
Grzegorz Grzybek commented on CAMEL-19564:
--
Fixed here:
https://github.com/apache/camel/commit/0be0a73e4f030eb11f060deea1e0027726c360e3
> xml-io-dsl: Allow routes to use beans loaded directly from source
> -
>
> Key: CAMEL-19564
> URL: https://issues.apache.org/jira/browse/CAMEL-19564
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.0.0
>
>
> With CAMEL-18189 we can now use {{}} elements in XMLs with top-level
> {{}} (or {{}}) elements.
> However it is not possible to load classes which come from {{*.java}} files
> passed to {{camel run}} because xml-io-dsl registers beans eagerly in
> {{org.apache.camel.spi.RoutesBuilderLoader#preParseRoute()}}.
> I have a PR which delays instantiation of such beans till when they're
> available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19564) xml-io-dsl: Allow routes to use beans loaded directly from source
Grzegorz Grzybek created CAMEL-19564:
Summary: xml-io-dsl: Allow routes to use beans loaded directly
from source
Key: CAMEL-19564
URL: https://issues.apache.org/jira/browse/CAMEL-19564
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
Fix For: 4.0.0
With CAMEL-18189 we can now use {{}} elements in XMLs with top-level
{{}} (or {{}}) elements.
However it is not possible to load classes which come from {{*.java}} files
passed to {{camel run}} because xml-io-dsl registers beans eagerly in
{{org.apache.camel.spi.RoutesBuilderLoader#preParseRoute()}}.
I have a PR which delays instantiation of such beans till when they're
available.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19041) camel-jbang - Run with runtime
[ https://issues.apache.org/jira/browse/CAMEL-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned CAMEL-19041: Assignee: (was: Grzegorz Grzybek) > camel-jbang - Run with runtime > -- > > Key: CAMEL-19041 > URL: https://issues.apache.org/jira/browse/CAMEL-19041 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.1.0 > > > So you can do camel run foo.java --runtime=spring-boot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19041) camel-jbang - Run with runtime
[
https://issues.apache.org/jira/browse/CAMEL-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17737132#comment-17737132
]
Grzegorz Grzybek commented on CAMEL-19041:
--
[~davsclaus], I'm unassigning this from myself - I have no idea how to switch
the runtime with single {{jbang run camel}} option... Picking up target runtime
should be more conscious decision than just an option:
* for Quarkus, much is happening at build time, so we need Maven (or Gradle?)
for this
* for Spring Boot we'd need to create the Camel context itself using Spring
bean (instead of instantiating DefaultCamelContext using camel-main (and
camel-kamelet-main)
> camel-jbang - Run with runtime
> --
>
> Key: CAMEL-19041
> URL: https://issues.apache.org/jira/browse/CAMEL-19041
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 4.1.0
>
>
> So you can do camel run foo.java --runtime=spring-boot
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19503) camel-jbang - Upgrade to maven-resolver 1.9.13
[ https://issues.apache.org/jira/browse/CAMEL-19503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-19503. -- Resolution: Fixed > camel-jbang - Upgrade to maven-resolver 1.9.13 > -- > > Key: CAMEL-19503 > URL: https://issues.apache.org/jira/browse/CAMEL-19503 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-RC1 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19503) camel-jbang - Upgrade to maven-resolver 1.9.13
Grzegorz Grzybek created CAMEL-19503: Summary: camel-jbang - Upgrade to maven-resolver 1.9.13 Key: CAMEL-19503 URL: https://issues.apache.org/jira/browse/CAMEL-19503 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 3.21.0, 4.0-RC1 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[ https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-18189. -- Resolution: Fixed The fixes are present in main branch for Camel 4.0. > camel-core - XML DSL for custom beans and to embed Camel routes in > same file > > > Key: CAMEL-18189 > URL: https://issues.apache.org/jira/browse/CAMEL-18189 > Project: Camel > Issue Type: New Feature > Components: camel-core-xml >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0 > > > We may consider a root tag such as that are Camel specific and > therefore works on all runtimes, where we can have basic support for > dependency injection with and also embed Camel and > and and etc all in the same file. > This can be handy for low-code projects with Camel K / Camel JBang. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[ https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17730064#comment-17730064 ] Grzegorz Grzybek commented on CAMEL-18189: -- Final PR with the documentation updates: https://github.com/apache/camel/pull/10283 > camel-core - XML DSL for custom beans and to embed Camel routes in > same file > > > Key: CAMEL-18189 > URL: https://issues.apache.org/jira/browse/CAMEL-18189 > Project: Camel > Issue Type: New Feature > Components: camel-core-xml >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: Future > > > We may consider a root tag such as that are Camel specific and > therefore works on all runtimes, where we can have basic support for > dependency injection with and also embed Camel and > and and etc all in the same file. > This can be handy for low-code projects with Camel K / Camel JBang. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[ https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18189: - Fix Version/s: 4.0 (was: Future) > camel-core - XML DSL for custom beans and to embed Camel routes in > same file > > > Key: CAMEL-18189 > URL: https://issues.apache.org/jira/browse/CAMEL-18189 > Project: Camel > Issue Type: New Feature > Components: camel-core-xml >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0 > > > We may consider a root tag such as that are Camel specific and > therefore works on all runtimes, where we can have basic support for > dependency injection with and also embed Camel and > and and etc all in the same file. > This can be handy for low-code projects with Camel K / Camel JBang. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[ https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729718#comment-17729718 ] Grzegorz Grzybek commented on CAMEL-18189: -- PR: https://github.com/apache/camel/pull/10268 > camel-core - XML DSL for custom beans and to embed Camel routes in > same file > > > Key: CAMEL-18189 > URL: https://issues.apache.org/jira/browse/CAMEL-18189 > Project: Camel > Issue Type: New Feature > Components: camel-core-xml >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: Future > > > We may consider a root tag such as that are Camel specific and > therefore works on all runtimes, where we can have basic support for > dependency injection with and also embed Camel and > and and etc all in the same file. > This can be handy for low-code projects with Camel K / Camel JBang. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727065#comment-17727065
]
Grzegorz Grzybek commented on CAMEL-18189:
--
CAMEL-16757 shows me that "beans" should be added rather through
{code:java}
org.apache.camel.builder.RouteConfigurationBuilder#configuration()
{code}
than through:
{code:java}
org.apache.camel.builder.RouteBuilder#configure()
{code}
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19340) camel-jbang - Upgrade to maven-resolver 1.9.10
[ https://issues.apache.org/jira/browse/CAMEL-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-19340. -- Resolution: Fixed > camel-jbang - Upgrade to maven-resolver 1.9.10 > -- > > Key: CAMEL-19340 > URL: https://issues.apache.org/jira/browse/CAMEL-19340 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-RC1 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19340) camel-jbang - Upgrade to maven-resolver 1.9.10
[ https://issues.apache.org/jira/browse/CAMEL-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19340: - Fix Version/s: (was: 3.20.5) > camel-jbang - Upgrade to maven-resolver 1.9.10 > -- > > Key: CAMEL-19340 > URL: https://issues.apache.org/jira/browse/CAMEL-19340 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-RC1 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19340) camel-jbang - Upgrade to maven-resolver 1.9.10
[ https://issues.apache.org/jira/browse/CAMEL-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19340: - Fix Version/s: 3.20.5 3.21.0 > camel-jbang - Upgrade to maven-resolver 1.9.10 > -- > > Key: CAMEL-19340 > URL: https://issues.apache.org/jira/browse/CAMEL-19340 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.20.5, 3.21.0, 4.0-RC1 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19340) camel-jbang - Upgrade to maven-resolver 1.9.10
[ https://issues.apache.org/jira/browse/CAMEL-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19340: - Fix Version/s: 4.0-RC1 > camel-jbang - Upgrade to maven-resolver 1.9.10 > -- > > Key: CAMEL-19340 > URL: https://issues.apache.org/jira/browse/CAMEL-19340 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 4.0-RC1 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12353177 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19329) Consider MiMa as alternative to pure maven-resolver
Grzegorz Grzybek created CAMEL-19329: Summary: Consider MiMa as alternative to pure maven-resolver Key: CAMEL-19329 URL: https://issues.apache.org/jira/browse/CAMEL-19329 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek See https://github.com/maveniverse/mima. This projects can help us prevent huge DI configuration where we provide one implementation of almost hundred of interfaces anyway. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716746#comment-17716746
]
Grzegorz Grzybek edited comment on CAMEL-18189 at 4/26/23 2:05 PM:
---
For a tiny moment I was thinking it's a matter of adding {{}}
({{org.apache.camel.model.BeansDefinition)}} in addition to existing {{}}
({{org.apache.camel.model.BeanDefinition}}) model.
The point is that {{org.apache.camel.reifier.BeanReifier#createProcessor()}}
which uses {{org.apache.camel.model.BeanDefinition}} to create a _bean_ is
using it to create a processor delegating to a method of a bean - there's no
way to configure properties of the bean created and whatever form is used:
{code:xml}
http://camel.apache.org/schema/spring; beanType="fqcn" />
{code}
{code:xml}
http://camel.apache.org/schema/spring; ref="ref-to-a-bean" />
{code}
the bean is created by the registry - using the first form (with classname),
the {{@Autowired}} Spring annotation is used and the bean may have the
properties injected, however there's no way to declare in XML the
properties/constructor arguments.
Existing {{}} means "bean processor which calls a bean (from the
registry) method" and it wouldn't be wise to add 2nd meaning: "bean definition
for a bean instance to put into the underlying registry"...
{{org.apache.camel.dsl.yaml.deserializers.BeansDeserializer#construct()}} is
actually doing what should be done, but narrowed to yaml DSL - it parses the
input (yaml) and adds the created beans (with proper {{properties}} handling -
though without constructor args for example) to a registry obtained from
{{org.apache.camel.CamelContext#getRegistry()}}... This doesn't help much in
general (for XML DSL).
In other words, IMO {{org.apache.camel.model.BeanDefinition}} can't be reused
to play two roles:
* bean processor
* bean definition (to populate the registry)
The naming curse is also visible here - for the new {{}} element:
* the XML element name should differ ({{}}?)
* the new class in {{org.apache.camel.model}} should rather be called
{{BeanDefinitionDefinition}} (:panic\:) and should NOT extend
{{org.apache.camel.model.ProcessorDefinition}}
Well, the journey continues.
was (Author: gzres):
For a tiny moment I was thinking it's a matter of adding {{}}
({{org.apache.camel.model.BeansDefinition)}} in addition to existing {{}}
({{org.apache.camel.model.BeanDefinition}}) model.
The point is that {{org.apache.camel.reifier.BeanReifier#createProcessor()}}
which uses {{org.apache.camel.model.BeanDefinition}} to create a _bean_ is
using it to create a processor delegating to a method of a bean - there's no
way to configure properties of the bean created and whatever form is used:
{code:xml}
http://camel.apache.org/schema/spring; beanType="fqcn" />
{code}
{code:xml}
http://camel.apache.org/schema/spring; ref="ref-to-a-bean" />
{code}
the bean is created by the registry - using the first form (with classname),
the {{@Autowired}} Spring annotation is used and the bean may have the
properties injected, however there's no way to declare in XML the
properties/constructor arguments.
Existing {{}} means "bean processor which calls a bean (from the
registry) method" and it wouldn't be wise to add 2nd meaning: "bean definition
for a bean instance to put into the underlying registry"...
{{org.apache.camel.dsl.yaml.deserializers.BeansDeserializer#construct()}} is
actually doing what should be done, but narrowed to yaml DSL - it parses the
input (yaml) and adds the created beans (with proper {{properties}} handling -
though without constructor args for example) to a registry obtained from
{{org.apache.camel.CamelContext#getRegistry()}}... This doesn't help much in
general (for XML DSL).
In other words, IMO {{org.apache.camel.model.BeanDefinition}} can't be reused
to play two roles:
* bean processor
* bean definition (to populate the registry)
The naming curse is also visible here - for the new {{}} element:
* the XML element name should differ ({{}}?)
* the new class in {{org.apache.camel.model}} should rather be called
{{BeanDefinitionDefinition}} (:panic:) and should NOT extend
{{org.apache.camel.model.ProcessorDefinition}}
Well, the journey continues.
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support
[jira] [Comment Edited] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716746#comment-17716746
]
Grzegorz Grzybek edited comment on CAMEL-18189 at 4/26/23 2:05 PM:
---
For a tiny moment I was thinking it's a matter of adding {{}}
({{org.apache.camel.model.BeansDefinition)}} in addition to existing {{}}
({{org.apache.camel.model.BeanDefinition}}) model.
The point is that {{org.apache.camel.reifier.BeanReifier#createProcessor()}}
which uses {{org.apache.camel.model.BeanDefinition}} to create a _bean_ is
using it to create a processor delegating to a method of a bean - there's no
way to configure properties of the bean created and whatever form is used:
{code:xml}
http://camel.apache.org/schema/spring; beanType="fqcn" />
{code}
{code:xml}
http://camel.apache.org/schema/spring; ref="ref-to-a-bean" />
{code}
the bean is created by the registry - using the first form (with classname),
the {{@Autowired}} Spring annotation is used and the bean may have the
properties injected, however there's no way to declare in XML the
properties/constructor arguments.
Existing {{}} means "bean processor which calls a bean (from the
registry) method" and it wouldn't be wise to add 2nd meaning: "bean definition
for a bean instance to put into the underlying registry"...
{{org.apache.camel.dsl.yaml.deserializers.BeansDeserializer#construct()}} is
actually doing what should be done, but narrowed to yaml DSL - it parses the
input (yaml) and adds the created beans (with proper {{properties}} handling -
though without constructor args for example) to a registry obtained from
{{org.apache.camel.CamelContext#getRegistry()}}... This doesn't help much in
general (for XML DSL).
In other words, IMO {{org.apache.camel.model.BeanDefinition}} can't be reused
to play two roles:
* bean processor
* bean definition (to populate the registry)
The naming curse is also visible here - for the new {{}} element:
* the XML element name should be different ({{}}?)
* the new class in {{org.apache.camel.model}} should rather be called
{{BeanDefinitionDefinition}} (:panic\:) and should NOT extend
{{org.apache.camel.model.ProcessorDefinition}}
Well, the journey continues.
was (Author: gzres):
For a tiny moment I was thinking it's a matter of adding {{}}
({{org.apache.camel.model.BeansDefinition)}} in addition to existing {{}}
({{org.apache.camel.model.BeanDefinition}}) model.
The point is that {{org.apache.camel.reifier.BeanReifier#createProcessor()}}
which uses {{org.apache.camel.model.BeanDefinition}} to create a _bean_ is
using it to create a processor delegating to a method of a bean - there's no
way to configure properties of the bean created and whatever form is used:
{code:xml}
http://camel.apache.org/schema/spring; beanType="fqcn" />
{code}
{code:xml}
http://camel.apache.org/schema/spring; ref="ref-to-a-bean" />
{code}
the bean is created by the registry - using the first form (with classname),
the {{@Autowired}} Spring annotation is used and the bean may have the
properties injected, however there's no way to declare in XML the
properties/constructor arguments.
Existing {{}} means "bean processor which calls a bean (from the
registry) method" and it wouldn't be wise to add 2nd meaning: "bean definition
for a bean instance to put into the underlying registry"...
{{org.apache.camel.dsl.yaml.deserializers.BeansDeserializer#construct()}} is
actually doing what should be done, but narrowed to yaml DSL - it parses the
input (yaml) and adds the created beans (with proper {{properties}} handling -
though without constructor args for example) to a registry obtained from
{{org.apache.camel.CamelContext#getRegistry()}}... This doesn't help much in
general (for XML DSL).
In other words, IMO {{org.apache.camel.model.BeanDefinition}} can't be reused
to play two roles:
* bean processor
* bean definition (to populate the registry)
The naming curse is also visible here - for the new {{}} element:
* the XML element name should differ ({{}}?)
* the new class in {{org.apache.camel.model}} should rather be called
{{BeanDefinitionDefinition}} (:panic\:) and should NOT extend
{{org.apache.camel.model.ProcessorDefinition}}
Well, the journey continues.
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716746#comment-17716746
]
Grzegorz Grzybek commented on CAMEL-18189:
--
For a tiny moment I was thinking it's a matter of adding {{}}
({{org.apache.camel.model.BeansDefinition)}} in addition to existing {{}}
({{org.apache.camel.model.BeanDefinition}}) model.
The point is that {{org.apache.camel.reifier.BeanReifier#createProcessor()}}
which uses {{org.apache.camel.model.BeanDefinition}} to create a _bean_ is
using it to create a processor delegating to a method of a bean - there's no
way to configure properties of the bean created and whatever form is used:
{code:xml}
http://camel.apache.org/schema/spring; beanType="fqcn" />
{code}
{code:xml}
http://camel.apache.org/schema/spring; ref="ref-to-a-bean" />
{code}
the bean is created by the registry - using the first form (with classname),
the {{@Autowired}} Spring annotation is used and the bean may have the
properties injected, however there's no way to declare in XML the
properties/constructor arguments.
Existing {{}} means "bean processor which calls a bean (from the
registry) method" and it wouldn't be wise to add 2nd meaning: "bean definition
for a bean instance to put into the underlying registry"...
{{org.apache.camel.dsl.yaml.deserializers.BeansDeserializer#construct()}} is
actually doing what should be done, but narrowed to yaml DSL - it parses the
input (yaml) and adds the created beans (with proper {{properties}} handling -
though without constructor args for example) to a registry obtained from
{{org.apache.camel.CamelContext#getRegistry()}}... This doesn't help much in
general (for XML DSL).
In other words, IMO {{org.apache.camel.model.BeanDefinition}} can't be reused
to play two roles:
* bean processor
* bean definition (to populate the registry)
The naming curse is also visible here - for the new {{}} element:
* the XML element name should differ ({{}}?)
* the new class in {{org.apache.camel.model}} should rather be called
{{BeanDefinitionDefinition}} (:panic:) and should NOT extend
{{org.apache.camel.model.ProcessorDefinition}}
Well, the journey continues.
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716310#comment-17716310
]
Grzegorz Grzybek edited comment on CAMEL-18189 at 4/25/23 3:17 PM:
---
bq. yaml-dsl already have -beans today where you can setup beans
{{org.apache.camel.dsl.yaml.deserializers.NamedBeanDefinition}} was indeed
added with CAMEL-16584.
But there's also
{{org.apache.camel.xml.in.ModelParser#doParseBeanDefinition()}} which deals
with {{org.apache.camel.model.BeanDefinition}}
But these look like the good old _beans_ you can use as processors and which
are configured in {{org.apache.camel.model.ProcessorDefinition}} (and derived
classes)...
I'm not sure how easy it'd be allow top level {{}} elements. On the other
hand it wouldn't be wise to duplicate the beans... Still thinking (you know - i
always have to re-learn Camel after getting back to its core after some
time...).
EDIT: {{org.apache.camel.model.BeanDefinition}} has already
{{@jakarta.xml.bind.annotation.XmlRootElement}} and can be used at top-level.
Indeed it should be a matter of top-level {{beans}} and handling it in
different DSLs... to be continued.
was (Author: gzres):
bq. yaml-dsl already have -beans today where you can setup beans
{{org.apache.camel.dsl.yaml.deserializers.NamedBeanDefinition}} was indeed
added with CAMEL-16584.
But there's also
{{org.apache.camel.xml.in.ModelParser#doParseBeanDefinition()}} which deals
with {{org.apache.camel.model.BeanDefinition}}
But these look like the good old _beans_ you can use as processors and which
are configured in {{org.apache.camel.model.ProcessorDefinition}} (and derived
classes)...
I'm not sure how easy it'd be allow top level {{}} elements. On the other
hand it wouldn't be wise to duplicate the beans... Still thinking (you know - i
always have to re-learn Camel after getting back to its core after some
time...).
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17716310#comment-17716310
]
Grzegorz Grzybek commented on CAMEL-18189:
--
bq. yaml-dsl already have -beans today where you can setup beans
{{org.apache.camel.dsl.yaml.deserializers.NamedBeanDefinition}} was indeed
added with CAMEL-16584.
But there's also
{{org.apache.camel.xml.in.ModelParser#doParseBeanDefinition()}} which deals
with {{org.apache.camel.model.BeanDefinition}}
But these look like the good old _beans_ you can use as processors and which
are configured in {{org.apache.camel.model.ProcessorDefinition}} (and derived
classes)...
I'm not sure how easy it'd be allow top level {{}} elements. On the other
hand it wouldn't be wise to duplicate the beans... Still thinking (you know - i
always have to re-learn Camel after getting back to its core after some
time...).
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17712944#comment-17712944
]
Grzegorz Grzybek commented on CAMEL-18189:
--
Thanks for the reminder :)
New {{beans}} is not a problem - the problem is whether it should much entire
{{org.springframework.beans.factory.config.BeanDefinition}} model or be some
kind of least common denominator with only:
* class name
* set of property values (with refs?)
* set of constructor arguments
* parent?
* depends-on?
* factory-method?
* post-construct / pre-destroy?
* scope (prototype / singleton)?
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18189) camel-core - XML DSL for custom beans and to embed Camel routes in same file
[
https://issues.apache.org/jira/browse/CAMEL-18189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17712944#comment-17712944
]
Grzegorz Grzybek edited comment on CAMEL-18189 at 4/17/23 8:07 AM:
---
Thanks for the reminder :)
New {{beans}} is not a problem - the problem is whether it should match/reflect
entire {{org.springframework.beans.factory.config.BeanDefinition}} model or be
some kind of least common denominator with only:
* class name
* set of property values (with refs?)
* set of constructor arguments
* parent?
* depends-on?
* factory-method?
* post-construct / pre-destroy?
* scope (prototype / singleton)?
was (Author: gzres):
Thanks for the reminder :)
New {{beans}} is not a problem - the problem is whether it should much entire
{{org.springframework.beans.factory.config.BeanDefinition}} model or be some
kind of least common denominator with only:
* class name
* set of property values (with refs?)
* set of constructor arguments
* parent?
* depends-on?
* factory-method?
* post-construct / pre-destroy?
* scope (prototype / singleton)?
> camel-core - XML DSL for custom beans and to embed Camel routes in
> same file
>
>
> Key: CAMEL-18189
> URL: https://issues.apache.org/jira/browse/CAMEL-18189
> Project: Camel
> Issue Type: New Feature
> Components: camel-core-xml
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: Future
>
>
> We may consider a root tag such as that are Camel specific and
> therefore works on all runtimes, where we can have basic support for
> dependency injection with and also embed Camel and
> and and etc all in the same file.
> This can be handy for low-code projects with Camel K / Camel JBang.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700163#comment-17700163 ] Grzegorz Grzybek commented on CAMEL-11767: -- Fixed [here|https://github.com/apache/camel/compare/8ed744ebad80c1250f63612f78eb9c6fc1d5f091%5E...b15fbe605729b7371485d936e4683c2fe589f8b1] in main branch. > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-11767. -- Resolution: Fixed > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-19123. -- Resolution: Fixed > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0, 4.0-M2 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700162#comment-17700162 ] Grzegorz Grzybek commented on CAMEL-19123: -- Fixed [here|https://github.com/apache/camel/commit/a47c5971232891ba33a1cee4f3ac6a7395663741] in main branch. > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767 ] Grzegorz Grzybek deleted comment on CAMEL-11767: -- was (Author: gzres): main branch was fine after https://github.com/apache/camel/commit/a6e94a37b4830 > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-11767. -- Resolution: Fixed main branch was fine after https://github.com/apache/camel/commit/a6e94a37b4830 > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reopened CAMEL-11767: -- > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19138) Maven 3.9.0 build fails with -Psourcecheck
[
https://issues.apache.org/jira/browse/CAMEL-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved CAMEL-19138.
--
Resolution: Fixed
{{main}} branch was fine after
https://github.com/apache/camel/commit/a6e94a37b4830.
> Maven 3.9.0 build fails with -Psourcecheck
> --
>
> Key: CAMEL-19138
> URL: https://issues.apache.org/jira/browse/CAMEL-19138
> Project: Camel
> Issue Type: Task
> Components: build system
>Affects Versions: 3.21.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> {noformat}
> [ERROR] Failed to execute goal
> net.revelc.code:impsort-maven-plugin:1.6.0:check (check) on project
> camel-tooling-util: Execution check of goal
> net.revelc.code:impsort-maven-plugin:1.6.0:check failed: A required class was
> missing while executing net.revelc.code:impsort-maven-plugin:1.6.0:check:
> org/codehaus/plexus/util/DirectoryScanner
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700118#comment-17700118 ] Grzegorz Grzybek commented on CAMEL-11767: -- Fixed [here|https://github.com/apache/camel/compare/01e47dfa85d04c22e7fe52ac30611ebb49637a98%5E...483525a2987578a6a24055059ff87e7ac2f9696c] in camel-3.x branch. > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19138) Maven 3.9.0 build fails with -Psourcecheck
[
https://issues.apache.org/jira/browse/CAMEL-19138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700115#comment-17700115
]
Grzegorz Grzybek commented on CAMEL-19138:
--
Fixed
[here|https://github.com/apache/camel/commit/5a652008ee1ef2f1eb9f34fcc01f3d973880a945]
in camel-3.x branch.
> Maven 3.9.0 build fails with -Psourcecheck
> --
>
> Key: CAMEL-19138
> URL: https://issues.apache.org/jira/browse/CAMEL-19138
> Project: Camel
> Issue Type: Task
> Components: build system
>Affects Versions: 3.21.0
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.21.0, 4.0-M3, 4.0
>
>
> {noformat}
> [ERROR] Failed to execute goal
> net.revelc.code:impsort-maven-plugin:1.6.0:check (check) on project
> camel-tooling-util: Execution check of goal
> net.revelc.code:impsort-maven-plugin:1.6.0:check failed: A required class was
> missing while executing net.revelc.code:impsort-maven-plugin:1.6.0:check:
> org/codehaus/plexus/util/DirectoryScanner
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17700113#comment-17700113 ] Grzegorz Grzybek commented on CAMEL-19123: -- Fixed [here|https://github.com/apache/camel/commit/1cae5b76126ebbf3e4c2eb607e121e19dbbf2064] in camel-3.x branch. > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699638#comment-17699638 ] Grzegorz Grzybek edited comment on CAMEL-19123 at 3/13/23 1:38 PM: --- PR for Camel 3.x: https://github.com/apache/camel/pull/9518 was (Author: gzres): PR: https://github.com/apache/camel/pull/9518 > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap instead of gradle)
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699639#comment-17699639 ] Grzegorz Grzybek commented on CAMEL-11767: -- PR for Camel 3.x: https://github.com/apache/camel/pull/9518 > camel-catalog-maven - Use real maven downloader (was: Maybe use shrinkwrap > instead of gradle) > - > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M3, 4.0 > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17699638#comment-17699638 ] Grzegorz Grzybek commented on CAMEL-19123: -- PR: https://github.com/apache/camel/pull/9518 > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19138) Maven 3.9.0 build fails with -Psourcecheck
Grzegorz Grzybek created CAMEL-19138:
Summary: Maven 3.9.0 build fails with -Psourcecheck
Key: CAMEL-19138
URL: https://issues.apache.org/jira/browse/CAMEL-19138
Project: Camel
Issue Type: Task
Affects Versions: 3.21.0
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
{noformat}
[ERROR] Failed to execute goal net.revelc.code:impsort-maven-plugin:1.6.0:check
(check) on project camel-tooling-util: Execution check of goal
net.revelc.code:impsort-maven-plugin:1.6.0:check failed: A required class was
missing while executing net.revelc.code:impsort-maven-plugin:1.6.0:check:
org/codehaus/plexus/util/DirectoryScanner
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697804#comment-17697804 ] Grzegorz Grzybek edited comment on CAMEL-19123 at 3/8/23 9:34 AM: -- Also it's worth noting that the wagon transport is marked as _ancient_ and native HTTP transport should be used: https://maven.apache.org/guides/mini/guide-http-settings.html While there's no need to switch entire Camel to rely on Maven 3.9.x, when using maven-resolver 1.9.x I'll try to use it in the modern way. cc: [~davsclaus] was (Author: gzres): Also it's worth noting that the wagon transport is marked as _ancient_ and native HTTP transport should be used: https://maven.apache.org/guides/mini/guide-http-settings.html While there's no need to switch entire Camel to rely on Maven 3.9.x, when using maven-resolver 1.9.x I'll try to use it in the modern way. > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697804#comment-17697804 ] Grzegorz Grzybek commented on CAMEL-19123: -- Also it's worth noting that the wagon transport is marked as _ancient_ and native HTTP transport should be used: https://maven.apache.org/guides/mini/guide-http-settings.html While there's no need to switch entire Camel to rely on Maven 3.9.x, when using maven-resolver 1.9.x I'll try to use it in the modern way. > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19123) camel-jbang - upgrade maven-resolver to 1.9.7
[ https://issues.apache.org/jira/browse/CAMEL-19123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19123: - Summary: camel-jbang - upgrade maven-resolver to 1.9.7 (was: camel-jbang - upgrade maven-resolver-api to 1.9.6) > camel-jbang - upgrade maven-resolver to 1.9.7 > - > > Key: CAMEL-19123 > URL: https://issues.apache.org/jira/browse/CAMEL-19123 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0-M2, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19123) camel-jbang - upgrade maven-resolver-api to 1.9.6
Grzegorz Grzybek created CAMEL-19123: Summary: camel-jbang - upgrade maven-resolver-api to 1.9.6 Key: CAMEL-19123 URL: https://issues.apache.org/jira/browse/CAMEL-19123 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 3.21.0, 4.0-M2, 4.0 No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643876#comment-17643876
]
Grzegorz Grzybek edited comment on CAMEL-11767 at 3/7/23 10:13 AM:
---
In theory, {{org.apache.camel.catalog.maven.DefaultMavenArtifactProvider}} can
be removed, because it's not used outside of one Syndesis integration test.
On the other hand, {{org.apache.camel.catalog.maven.MavenVersionManager}} and
similar {{com.github.cameltooling.idea.service.CamelMavenVersionManager}} (and
indirectly {{com.github.cameltooling.lsp.internal.CamelTextDocumentService()}}
can be rewritten to not use Grape.
camel-catalog library can provide different resolver, which is used already in
dsl/camel-camelet-main
({{org.apache.camel.main.download.MavenDependencyDownloader}}).
Because dsl/camel-camelet-main depends on catalog/camel-catalog, which in turn
uses (indirectly) camel-api, camel-util, we have lot of places to move
{{org.apache.camel.main.download.MavenDependencyDownloader}} (and what's
important, also {{org.apache.camel.main.injection.DIRegistry}}) to.
was (Author: gzres):
In theory, {{org.apache.camel.catalog.maven.DefaultMavenArtifactProvider}} can
be removed, because it's not used outside of one Syndesis integration test.
On the other hand, {{org.apache.camel.catalog.maven.MavenVersionManager}} and
similar {{com.github.cameltooling.idea.service.CamelMavenVersionManager}} (and
indirectly {{com.github.cameltooling.lsp.internal.CamelTextDocumentService()}}
can be rewritten to not use Grape.
camel-catalog library can provide different resolved, which is used already in
dsl/camel-camelet-main
({{org.apache.camel.main.download.MavenDependencyDownloader}}).
Because dsl/camel-camelet-main depends on catalog/camel-catalog, which in turn
uses (indirectly) camel-api, camel-util, we have lot of places to move
{{org.apache.camel.main.download.MavenDependencyDownloader}} (and what's
important, also {{org.apache.camel.main.injection.DIRegistry}}) to.
> camel-catalog-maven - Maybe use shrinkwrap instead of gradle
>
>
> Key: CAMEL-11767
> URL: https://issues.apache.org/jira/browse/CAMEL-11767
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog, tooling
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Minor
> Fix For: 3.x
>
>
> We can look at using shrinkwrap resolver which has a nice API for downloading
> Maven JARs. We just need that to be able to download the camel-catalog JAR of
> a given version
> https://github.com/shrinkwrap/resolver
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19041) camel-jbang - Run with runtime
[ https://issues.apache.org/jira/browse/CAMEL-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696971#comment-17696971 ] Grzegorz Grzybek commented on CAMEL-19041: -- [~davsclaus] I had CAMEL-18662 on my todo list, but not before resolving CAMEL-18189. > camel-jbang - Run with runtime > -- > > Key: CAMEL-19041 > URL: https://issues.apache.org/jira/browse/CAMEL-19041 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0-M3, 4.0 > > > So you can do camel run foo.java --runtime=spring-boot -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17696555#comment-17696555 ] Grzegorz Grzybek commented on CAMEL-11767: -- yes yes, I'm just working on it ;) (I was busy with the versions so far...) > camel-catalog-maven - Maybe use shrinkwrap instead of gradle > > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Minor > Fix For: 3.x > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19092) camel-jbang - upgrade maven-resolver-api to 1.9.5
[ https://issues.apache.org/jira/browse/CAMEL-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-19092. -- Resolution: Fixed > camel-jbang - upgrade maven-resolver-api to 1.9.5 > - > > Key: CAMEL-19092 > URL: https://issues.apache.org/jira/browse/CAMEL-19092 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19092) camel-jbang - upgrade maven-resolver-api to 1.9.5
[ https://issues.apache.org/jira/browse/CAMEL-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19092: - Description: No API changes between 1.9.4 and 1.9.5. (was: We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code should be changed a bit. It may be easier to do this on camel-3.x branch as main is for v4 and its more unstable at the moment) > camel-jbang - upgrade maven-resolver-api to 1.9.5 > - > > Key: CAMEL-19092 > URL: https://issues.apache.org/jira/browse/CAMEL-19092 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > No API changes between 1.9.4 and 1.9.5. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19092) camel-jbang - upgrade maven-resolver-api to 1.9.5
Grzegorz Grzybek created CAMEL-19092: Summary: camel-jbang - upgrade maven-resolver-api to 1.9.5 Key: CAMEL-19092 URL: https://issues.apache.org/jira/browse/CAMEL-19092 Project: Camel Issue Type: Dependency upgrade Components: camel-jbang Reporter: Grzegorz Grzybek Assignee: Grzegorz Grzybek Fix For: 3.21.0, 4.0-M1, 4.0 We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code should be changed a bit. It may be easier to do this on camel-3.x branch as main is for v4 and its more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19092) camel-jbang - upgrade maven-resolver-api to 1.9.5
[ https://issues.apache.org/jira/browse/CAMEL-19092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-19092: - Fix Version/s: (was: 4.0-M1) > camel-jbang - upgrade maven-resolver-api to 1.9.5 > - > > Key: CAMEL-19092 > URL: https://issues.apache.org/jira/browse/CAMEL-19092 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.4
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-18880. -- Resolution: Fixed > camel-jbang - upgrade maven-resolver-api to 1.9.4 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.4
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17677360#comment-17677360 ] Grzegorz Grzybek commented on CAMEL-18880: -- PR to upgrade to 1.9.4 for camel 4: https://github.com/apache/camel/pull/9117 PR to upgrade to 1.9.4 for camel 3: https://github.com/apache/camel/pull/9119 > camel-jbang - upgrade maven-resolver-api to 1.9.4 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.4
[
https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676527#comment-17676527
]
Grzegorz Grzybek edited comment on CAMEL-18880 at 1/13/23 9:03 AM:
---
[~cstamas] thanks for info - I already checked with 1.9.4 and there will be one
little change needed:
1.9.2:
{code:java}
registry.bind(GAVNameMapperProvider.NAME, NameMapper.class, new
GAVNameMapperProvider().get());
{code}
1.9.4:
{code:java}
registry.bind(NameMappers.GAV_NAME, NameMapper.class,
NameMappers.gavNameMapper());
{code}
was (Author: gzres):
[~cstamas] thanks for info - I already checked with 1.9.4 and there's one
little change needed:
1.9.2:
{code:java}
registry.bind(GAVNameMapperProvider.NAME, NameMapper.class, new
GAVNameMapperProvider().get());
{code}
1.9.4:
{code:java}
registry.bind(NameMappers.GAV_NAME, NameMapper.class,
NameMappers.gavNameMapper());
{code}
> camel-jbang - upgrade maven-resolver-api to 1.9.4
> -
>
> Key: CAMEL-18880
> URL: https://issues.apache.org/jira/browse/CAMEL-18880
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-jbang
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.21.0, 4.0
>
>
> We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code
> should be changed a bit.
> It may be easier to do this on camel-3.x branch as main is for v4 and its
> more unstable at the moment
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.4
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676528#comment-17676528 ] Grzegorz Grzybek commented on CAMEL-18880: -- I'll resolve this one when Maven Resolver 1.9.4 is released. > camel-jbang - upgrade maven-resolver-api to 1.9.4 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[
https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676527#comment-17676527
]
Grzegorz Grzybek commented on CAMEL-18880:
--
[~cstamas] thanks for info - I already checked with 1.9.4 and there's one
little change needed:
1.9.2:
{code:java}
registry.bind(GAVNameMapperProvider.NAME, NameMapper.class, new
GAVNameMapperProvider().get());
{code}
1.9.4:
{code:java}
registry.bind(NameMappers.GAV_NAME, NameMapper.class,
NameMappers.gavNameMapper());
{code}
> camel-jbang - upgrade maven-resolver-api to 1.9.2
> -
>
> Key: CAMEL-18880
> URL: https://issues.apache.org/jira/browse/CAMEL-18880
> Project: Camel
> Issue Type: Dependency upgrade
> Components: camel-jbang
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 3.21.0, 4.0
>
>
> We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code
> should be changed a bit.
> It may be easier to do this on camel-3.x branch as main is for v4 and its
> more unstable at the moment
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.4
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18880: - Summary: camel-jbang - upgrade maven-resolver-api to 1.9.4 (was: camel-jbang - upgrade maven-resolver-api to 1.9.2) > camel-jbang - upgrade maven-resolver-api to 1.9.4 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676514#comment-17676514 ] Grzegorz Grzybek edited comment on CAMEL-18880 at 1/13/23 8:55 AM: --- PR for main branch (4.0): https://github.com/apache/camel/pull/9075 PR for camel-3.x branch: https://github.com/apache/camel/pull/9078 was (Author: gzres): PR for main branch (4.0): https://github.com/apache/camel/pull/9075 > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17676514#comment-17676514 ] Grzegorz Grzybek commented on CAMEL-18880: -- PR for main branch (4.0): https://github.com/apache/camel/pull/9075 > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Major > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18880: - Priority: Critical (was: Major) > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Critical > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18880) camel-jbang - upgrade maven-resolver-api to 1.9.2
[ https://issues.apache.org/jira/browse/CAMEL-18880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17675599#comment-17675599 ] Grzegorz Grzybek commented on CAMEL-18880: -- Sure - I should be able to do it this week. > camel-jbang - upgrade maven-resolver-api to 1.9.2 > - > > Key: CAMEL-18880 > URL: https://issues.apache.org/jira/browse/CAMEL-18880 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Critical > Fix For: 3.21.0, 4.0 > > > We use 1.8.2 and there is a 1.9.2. It has some changed internals so the code > should be changed a bit. > It may be easier to do this on camel-3.x branch as main is for v4 and its > more unstable at the moment -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644817#comment-17644817
]
Grzegorz Grzybek edited comment on CAMEL-11767 at 12/8/22 1:58 PM:
---
For the record - here's how camel-catalog jar is downloaded by {{Grape.grab()}}:
{noformat}
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at java.io.FileOutputStream.(FileOutputStream.java:222)
at java.io.FileOutputStream.(FileOutputStream.java:187)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:275)
at
org.apache.ivy.util.url.HttpClientHandler.download(HttpClientHandler.java:164)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:254)
at
org.apache.ivy.plugins.repository.url.URLRepository.get(URLRepository.java:68)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.get(RepositoryResolver.java:197)
at
org.apache.ivy.plugins.resolver.BasicResolver.getAndCheck(BasicResolver.java:976)
at
org.apache.ivy.plugins.resolver.BasicResolver$6.download(BasicResolver.java:1150)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:1040)
at
org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
at
org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:408)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:354)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:442)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:256)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:236)
at groovy.grape.Grape.grab(Grape.java:153)
at
org.apache.camel.catalog.maven.MavenVersionManager.loadVersion(MavenVersionManager.java:119)
at
org.apache.camel.catalog.maven.MavenVersionManagerManualTest.testLoadVersion(MavenVersionManagerManualTest.java:46)
...
{noformat}
And the artifact is downloaded into
{{~/.groovy/grapes/org.apache.camel/camel-catalog/jars/camel-catalog-2.17.2.jar.part}}
was (Author: gzres):
For the record - here's how camel-catalog jar is downloaded by {{Grape.grab()}}:
{noformat}
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at java.io.FileOutputStream.(FileOutputStream.java:222)
at java.io.FileOutputStream.(FileOutputStream.java:187)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:275)
at
org.apache.ivy.util.url.HttpClientHandler.download(HttpClientHandler.java:164)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:254)
at
org.apache.ivy.plugins.repository.url.URLRepository.get(URLRepository.java:68)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.get(RepositoryResolver.java:197)
at
org.apache.ivy.plugins.resolver.BasicResolver.getAndCheck(BasicResolver.java:976)
at
org.apache.ivy.plugins.resolver.BasicResolver$6.download(BasicResolver.java:1150)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:1040)
at
org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
at
org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:408)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:354)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:442)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:256)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:236)
at groovy.grape.Grape.grab(Grape.java:153)
at
org.apache.camel.catalog.maven.MavenVersionManager.loadVersion(MavenVersionManager.java:119)
at
org.apache.camel.catalog.maven.MavenVersionManagerManualTest.testLoadVersion(MavenVersionManagerManualTest.java:46)
...
{noformat}
> camel-catalog-maven - Maybe use shrinkwrap instead of gradle
>
>
> Key: CAMEL-11767
>
[jira] [Comment Edited] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644817#comment-17644817
]
Grzegorz Grzybek edited comment on CAMEL-11767 at 12/8/22 1:58 PM:
---
For the record - here's how camel-catalog jar is downloaded by {{Grape.grab()}}:
{noformat}
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at java.io.FileOutputStream.(FileOutputStream.java:222)
at java.io.FileOutputStream.(FileOutputStream.java:187)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:275)
at
org.apache.ivy.util.url.HttpClientHandler.download(HttpClientHandler.java:164)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:254)
at
org.apache.ivy.plugins.repository.url.URLRepository.get(URLRepository.java:68)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.get(RepositoryResolver.java:197)
at
org.apache.ivy.plugins.resolver.BasicResolver.getAndCheck(BasicResolver.java:976)
at
org.apache.ivy.plugins.resolver.BasicResolver$6.download(BasicResolver.java:1150)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:1040)
at
org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
at
org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:408)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:354)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:442)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:256)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:236)
at groovy.grape.Grape.grab(Grape.java:153)
at
org.apache.camel.catalog.maven.MavenVersionManager.loadVersion(MavenVersionManager.java:119)
at
org.apache.camel.catalog.maven.MavenVersionManagerManualTest.testLoadVersion(MavenVersionManagerManualTest.java:46)
...
{noformat}
And the artifact is downloaded into
{{~/.groovy/grapes/org.apache.camel/camel-catalog/jars/camel-catalog-2.17.2.jar.part}}
(and then renamed of course).
was (Author: gzres):
For the record - here's how camel-catalog jar is downloaded by {{Grape.grab()}}:
{noformat}
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at java.io.FileOutputStream.(FileOutputStream.java:222)
at java.io.FileOutputStream.(FileOutputStream.java:187)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:275)
at
org.apache.ivy.util.url.HttpClientHandler.download(HttpClientHandler.java:164)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:254)
at
org.apache.ivy.plugins.repository.url.URLRepository.get(URLRepository.java:68)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.get(RepositoryResolver.java:197)
at
org.apache.ivy.plugins.resolver.BasicResolver.getAndCheck(BasicResolver.java:976)
at
org.apache.ivy.plugins.resolver.BasicResolver$6.download(BasicResolver.java:1150)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:1040)
at
org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
at
org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:408)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:354)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:442)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:256)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:236)
at groovy.grape.Grape.grab(Grape.java:153)
at
org.apache.camel.catalog.maven.MavenVersionManager.loadVersion(MavenVersionManager.java:119)
at
org.apache.camel.catalog.maven.MavenVersionManagerManualTest.testLoadVersion(MavenVersionManagerManualTest.java:46)
...
{noformat}
And the artifact is downloaded into
{{~/.groovy/grapes/org.apache.camel/camel-catalog/jars/camel-catalog-2.17.2.jar.part}}
> camel-catalog-maven -
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644817#comment-17644817
]
Grzegorz Grzybek commented on CAMEL-11767:
--
For the record - here's how camel-catalog jar is downloaded by {{Grape.grab()}}:
{noformat}
"main@1" prio=5 tid=0x1 nid=NA runnable
java.lang.Thread.State: RUNNABLE
at java.io.FileOutputStream.(FileOutputStream.java:222)
at java.io.FileOutputStream.(FileOutputStream.java:187)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:275)
at
org.apache.ivy.util.url.HttpClientHandler.download(HttpClientHandler.java:164)
at org.apache.ivy.util.FileUtil.copy(FileUtil.java:254)
at
org.apache.ivy.plugins.repository.url.URLRepository.get(URLRepository.java:68)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.get(RepositoryResolver.java:197)
at
org.apache.ivy.plugins.resolver.BasicResolver.getAndCheck(BasicResolver.java:976)
at
org.apache.ivy.plugins.resolver.BasicResolver$6.download(BasicResolver.java:1150)
at
org.apache.ivy.core.cache.DefaultRepositoryCacheManager.download(DefaultRepositoryCacheManager.java:1040)
at
org.apache.ivy.plugins.resolver.BasicResolver.download(BasicResolver.java:836)
at
org.apache.ivy.plugins.resolver.RepositoryResolver.download(RepositoryResolver.java:305)
at
org.apache.ivy.plugins.resolver.IBiblioResolver.download(IBiblioResolver.java:563)
at
org.apache.ivy.core.resolve.ResolveEngine.downloadArtifacts(ResolveEngine.java:408)
at
org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:354)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:442)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:625)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:592)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:256)
at groovy.grape.GrapeIvy.grab(GrapeIvy.groovy:236)
at groovy.grape.Grape.grab(Grape.java:153)
at
org.apache.camel.catalog.maven.MavenVersionManager.loadVersion(MavenVersionManager.java:119)
at
org.apache.camel.catalog.maven.MavenVersionManagerManualTest.testLoadVersion(MavenVersionManagerManualTest.java:46)
...
{noformat}
> camel-catalog-maven - Maybe use shrinkwrap instead of gradle
>
>
> Key: CAMEL-11767
> URL: https://issues.apache.org/jira/browse/CAMEL-11767
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog, tooling
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Minor
> Fix For: 3.x
>
>
> We can look at using shrinkwrap resolver which has a nice API for downloading
> Maven JARs. We just need that to be able to download the camel-catalog JAR of
> a given version
> https://github.com/shrinkwrap/resolver
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643876#comment-17643876
]
Grzegorz Grzybek commented on CAMEL-11767:
--
In theory, {{org.apache.camel.catalog.maven.DefaultMavenArtifactProvider}} can
be removed, because it's not used outside of one Syndesis integration test.
On the other hand, {{org.apache.camel.catalog.maven.MavenVersionManager}} and
similar {{com.github.cameltooling.idea.service.CamelMavenVersionManager}} (and
indirectly {{com.github.cameltooling.lsp.internal.CamelTextDocumentService()}}
can be rewritten to not use Grape.
camel-catalog library can provide different resolved, which is used already in
dsl/camel-camelet-main
({{org.apache.camel.main.download.MavenDependencyDownloader}}).
Because dsl/camel-camelet-main depends on catalog/camel-catalog, which in turn
uses (indirectly) camel-api, camel-util, we have lot of places to move
{{org.apache.camel.main.download.MavenDependencyDownloader}} (and what's
important, also {{org.apache.camel.main.injection.DIRegistry}}) to.
> camel-catalog-maven - Maybe use shrinkwrap instead of gradle
>
>
> Key: CAMEL-11767
> URL: https://issues.apache.org/jira/browse/CAMEL-11767
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog, tooling
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Minor
> Fix For: 3.x
>
>
> We can look at using shrinkwrap resolver which has a nice API for downloading
> Maven JARs. We just need that to be able to download the camel-catalog JAR of
> a given version
> https://github.com/shrinkwrap/resolver
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[
https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643867#comment-17643867
]
Grzegorz Grzybek commented on CAMEL-11767:
--
For the context, {{groovy.grape.Grape#grab()}} is used in:
h5. Directly in Camel 3.x
* {{camel-grape}} component (that's obvious)
* {{catalog/camel-catalog-maven}}:
**
org.apache.camel.catalog.maven.DefaultMavenArtifactProvider#addArtifactToCatalog()
- implementation of
org.apache.camel.catalog.maven.MavenArtifactProvider#addArtifactToCatalog()
**
org.apache.camel.catalog.maven.MavenVersionManager#loadRuntimeProviderVersion()
- implementation of
org.apache.camel.catalog.VersionManager#loadRuntimeProviderVersion()
** org.apache.camel.catalog.maven.MavenVersionManager#loadVersion() -
implementation of org.apache.camel.catalog.VersionManager#loadVersion()
h5. Camel 2.x
* There is
platforms/camel-catalog-rest/src/main/java/org/apache/camel/catalog/rest/CamelCatalogRest.java,
but it was removed in https://github.com/apache/camel/commit/28e7cc87beb9
h5. Indirectly, in other projects that use Camel 3.x
* camel-tooling/camel-idea-plugin
**
com.github.cameltooling.idea.service.CamelMavenVersionManager#loadRuntimeProviderVersion
- implementation of
org.apache.camel.catalog.VersionManager#loadRuntimeProviderVersion()
** com.github.cameltooling.idea.service.CamelMavenVersionManager#loadVersion()
- implementation of org.apache.camel.catalog.VersionManager#loadVersion()
**
com.github.cameltooling.idea.runner.debugger.CamelDebuggerPatcher.ExecutionMode#autoAddCamelDebugger()
- in
com.github.cameltooling.idea.runner.debugger.CamelDebuggerPatcher.ExecutionMode#JAVA
enum
* camel-tooling/camel-language-server
**
com.github.cameltooling.lsp.internal.CamelTextDocumentService#updateCatalogVersion()
instantiates {{org.apache.camel.catalog.maven.MavenVersionManager}}
* syndesisio/connectors was using camel-catalog, but it's no longer doing it
(or rather the project is archived and is using Camel 2 anyway)
* syndesisio/syndesis-rest was using camel-catalog, but it's no longer doing it
(or rather the project is archived and is using Camel 2 anyway)
> camel-catalog-maven - Maybe use shrinkwrap instead of gradle
>
>
> Key: CAMEL-11767
> URL: https://issues.apache.org/jira/browse/CAMEL-11767
> Project: Camel
> Issue Type: Improvement
> Components: camel-catalog, tooling
>Reporter: Claus Ibsen
>Assignee: Grzegorz Grzybek
>Priority: Minor
> Fix For: 3.x
>
>
> We can look at using shrinkwrap resolver which has a nice API for downloading
> Maven JARs. We just need that to be able to download the camel-catalog JAR of
> a given version
> https://github.com/shrinkwrap/resolver
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-11767) camel-catalog-maven - Maybe use shrinkwrap instead of gradle
[ https://issues.apache.org/jira/browse/CAMEL-11767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned CAMEL-11767: Assignee: Grzegorz Grzybek > camel-catalog-maven - Maybe use shrinkwrap instead of gradle > > > Key: CAMEL-11767 > URL: https://issues.apache.org/jira/browse/CAMEL-11767 > Project: Camel > Issue Type: Improvement > Components: camel-catalog, tooling >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Minor > Fix For: 3.x > > > We can look at using shrinkwrap resolver which has a nice API for downloading > Maven JARs. We just need that to be able to download the camel-catalog JAR of > a given version > https://github.com/shrinkwrap/resolver -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-16221) Rethink endpoints URI usage for camel internals
[
https://issues.apache.org/jira/browse/CAMEL-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634871#comment-17634871
]
Grzegorz Grzybek edited comment on CAMEL-16221 at 11/16/22 2:47 PM:
Just to provide some summary:
* if there are two slashes ({{//}}) after first colon, what follows is _always_
the _authority_ ({{java.net.URI#getAuthority()}}), so:
** {{file:/path/to/file.txt}} - authority is null and {{/path/to/file.txt}} is
the path
** {{file://path/to/file.txt}} - {{path}} is the authority, {{/to/file.txt}} is
the path
** {{file:///path/to/file.txt}} - authority is null and the path is
{{/path/to/file.txt}}
* if there's no slash after first colon, the URI is always _opaque_ - it never
has any path ({{java.net.URI#getPath()}}), it has only three components:
** scheme
** scheme-specific part
** fragment
* if there's a scheme, the URI is always absolute (whether or not there's a
slash after scheme)
* if there's no scheme, the URI is never absolute (even in
{{java.net.URI.create("/hello")}}).
was (Author: gzres):
Just to provide some summary:
* if there are two slashes ({{//}}) after first colon, what follows is _always_
the _authority_ ({{java.net.URI#getAuthority()}}), so:
** {{file:/path/to/file.txt}} - authority is null and {{/path/to/file.txt}} is
the path
** {{file://path/to/file.txt}} - {{path}} is the authority, {{/to/file.txt}} is
the path
** {{file:///path/to/file.txt}} - authority is null and the path is
{{/path/to/file.txt}}
* if there's no slash after first colon, the URI is always _opaque_ - it never
has any path ({{java.net.URI#getPath()}}), it has only three components:
** scheme
** scheme-specific part
** fragment
* if there's a scheme, the URI is always absolute (whether or not there's a
slash after scheme)
* if there's no scheme, the URI is never absolute (even in
{{java.net.URI.create("/hello")}}.
> Rethink endpoints URI usage for camel internals
> ---
>
> Key: CAMEL-16221
> URL: https://issues.apache.org/jira/browse/CAMEL-16221
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 4.0
>
>
> As today URIs are the primary mechanism Camel uses internally to describe
> endpoints but I think it is time to re-consider the dependency on URIs for
> camel internals and leave the URIs as an external representation of endpoints
> As example:
> - the Endpoint DSL is required to generate the related endpoint URI to
> leverage Camel's APIs but to create an endpoint, the schema and a map of
> options, would be more than enough.
> - components that wrap other components, such as kamelets, master & co may
> need to re-create URIs to create instances of the delegated endpoints which
> is cumbersome as there's lot of options to take into account (RAW,
> url-encoding, placeholders)
> - the YAML DSL and camel-kafka-connectors are using and Endpoint DSL alike
> syntax where a user can define endpoints by scheme + option pairs without the
> need of writing URIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-16221) Rethink endpoints URI usage for camel internals
[
https://issues.apache.org/jira/browse/CAMEL-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634871#comment-17634871
]
Grzegorz Grzybek commented on CAMEL-16221:
--
Just to provide some summary:
* if there are two slashes ({{//}}) after first colon, what follows is _always_
the _authority_ ({{java.net.URI#getAuthority()}}), so:
** {{file:/path/to/file.txt}} - authority is null and {{/path/to/file.txt}} is
the path
** {{file://path/to/file.txt}} - {{path}} is the authority, {{/to/file.txt}} is
the path
** {{file:///path/to/file.txt}} - authority is null and the path is
{{/path/to/file.txt}}
* if there's no slash after first colon, the URI is always _opaque_ - it never
has any path ({{java.net.URI#getPath()}}), it has only three components:
** scheme
** scheme-specific part
** fragment
* if there's a scheme, the URI is always absolute (whether or not there's a
slash after scheme)
* if there's no scheme, the URI is never absolute (even in
{{java.net.URI.create("/hello")}}.
> Rethink endpoints URI usage for camel internals
> ---
>
> Key: CAMEL-16221
> URL: https://issues.apache.org/jira/browse/CAMEL-16221
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 4.0
>
>
> As today URIs are the primary mechanism Camel uses internally to describe
> endpoints but I think it is time to re-consider the dependency on URIs for
> camel internals and leave the URIs as an external representation of endpoints
> As example:
> - the Endpoint DSL is required to generate the related endpoint URI to
> leverage Camel's APIs but to create an endpoint, the schema and a map of
> options, would be more than enough.
> - components that wrap other components, such as kamelets, master & co may
> need to re-create URIs to create instances of the delegated endpoints which
> is cumbersome as there's lot of options to take into account (RAW,
> url-encoding, placeholders)
> - the YAML DSL and camel-kafka-connectors are using and Endpoint DSL alike
> syntax where a user can define endpoints by scheme + option pairs without the
> need of writing URIs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-15616) camel-saxon - Upgrade to Saxon 11.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved CAMEL-15616. -- Resolution: Fixed > camel-saxon - Upgrade to Saxon 11.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Minor > Fix For: 3.20.0 > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-15616) camel-saxon - Upgrade to Saxon 11.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17620369#comment-17620369 ] Grzegorz Grzybek commented on CAMEL-15616: -- PRs: * https://github.com/apache/camel/pull/8580 * https://github.com/apache/camel-karaf/pull/201 * https://github.com/apache/camel-spring-boot/pull/649 > camel-saxon - Upgrade to Saxon 11.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Minor > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-15616) camel-saxon - Upgrade to Saxon 11.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned CAMEL-15616: Assignee: Grzegorz Grzybek (was: Ramu) > camel-saxon - Upgrade to Saxon 11.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Grzegorz Grzybek >Priority: Minor > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-15616) camel-saxon - Upgrade to Saxon 11.x
[ https://issues.apache.org/jira/browse/CAMEL-15616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-15616: - Summary: camel-saxon - Upgrade to Saxon 11.x (was: camel-saxon - Upgrade to Saxon 10.x) > camel-saxon - Upgrade to Saxon 11.x > --- > > Key: CAMEL-15616 > URL: https://issues.apache.org/jira/browse/CAMEL-15616 > Project: Camel > Issue Type: Improvement > Components: camel-saxon >Reporter: Claus Ibsen >Assignee: Ramu >Priority: Minor > Fix For: 3.x > > > We are using 9.9.x but there is a 10.x release out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615896#comment-17615896
]
Grzegorz Grzybek edited comment on CAMEL-18603 at 10/12/22 4:52 AM:
The problem is that there are two classloaders involved:
* one is the app classloader containing JARs being part of {{-classpath}}
prepared by JBang itself - this involves all transitive dependencies of the
{{DEPS}} specified in {{dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java}}
* the other one is
{{org.apache.camel.main.download.DependencyDownloaderClassLoader}} prepared for
the camel context created for {{jbang run camel@camel run}} command.
camel-kamelet-utils was not seeing the amazonsdk jars, because of two different
classloaders.
When I removed {{org.apache.camel.kamelets:camel-kamelets-utils}} from
{{main.CamelJBang}} and added it to the route itself:
{code:yaml}
# camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
# camel-k: dependency=mvn:org.apache.camel.kamelets:camel-kamelets-utils:0.9.0
- route:
from:
uri: "kamelet:kafka-not-secured-source"
...
{code}
everything worked fine.
was (Author: gzres):
The problem is that there are two classloaders involved:
* one is the app classloader containing JARs being part of {{-classpath}}
prepared by JBang itself - this involves all transitive dependencies of the
{{DEPS}} specified in {{dsl/camel-jbang/camel-jbang-main/dist/CamelJBang.java}}
* the other one is
{{org.apache.camel.main.download.DependencyDownloaderClassLoader}} prepared for
the camel context created for {{jbang camel run}} command.
camel-kamelet-utils was not seeing the amazonsdk jars, because of two different
classloaders.
When I removed {{org.apache.camel.kamelets:camel-kamelets-utils}} from
{{main.CamelJBang}} and added it to the route itself:
{code:yaml}
# camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
# camel-k: dependency=mvn:org.apache.camel.kamelets:camel-kamelets-utils:0.9.0
- route:
from:
uri: "kamelet:kafka-not-secured-source"
...
{code}
everything worked fine.
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615926#comment-17615926
]
Grzegorz Grzybek commented on CAMEL-18603:
--
[~nfilotto] sorry for the mess - it was mistaken
(https://www.getdroidtips.com/logitech-g502-right-left-click-not-holding/)
drag of entire folder into Jira - a chance 1 in a million, but just
happened...
I created CAMEL-18606, moved the attachments there (because it was hard to
remove one by one). Please delete CAMEL-18606 (cc: [~davsclaus], [~acosentino]).
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17615925#comment-17615925
]
Grzegorz Grzybek commented on CAMEL-18603:
--
If {{camel-aws2-ddb}} wasn't a provided dependency of camel-kamelets-utils:
{code:xml}
org.apache.camel
camel-aws2-ddb
provided
{code}
it'd work as well, because JBang itself would add it to AppClassPath together
with {{software.amazon.awssdk:dynamodb}}.
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-18603:
-
Attachment: (was: source-to-classes.tab.len)
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-18603:
-
Attachment: (was: subtypes.tab_i.len)
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18606) task to remove attachments from CAMEL-18603
[ https://issues.apache.org/jira/browse/CAMEL-18606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18606: - Attachment: supertypes.tab_i.len > task to remove attachments from CAMEL-18603 > --- > > Key: CAMEL-18606 > URL: https://issues.apache.org/jira/browse/CAMEL-18606 > Project: Camel > Issue Type: Task >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Attachments: KotlinCompilationConfiguration$1$1-1.class, > KotlinCompilationConfiguration$1$1-1.class, > KotlinCompilationConfiguration$1$1.class, > KotlinCompilationConfiguration$1$1.class, > KotlinCompilationConfiguration$1$2-1.class, > KotlinCompilationConfiguration$1$2-1.class, > KotlinCompilationConfiguration$1$2.class, > KotlinCompilationConfiguration$1$2.class, > KotlinCompilationConfiguration$1-1.class, > KotlinCompilationConfiguration$1-1.class, > KotlinCompilationConfiguration$1.class, > KotlinCompilationConfiguration$1.class, > KotlinCompilationConfiguration-1.class, > KotlinCompilationConfiguration-1.class, KotlinCompilationConfiguration.class, > KotlinCompilationConfiguration.class, KotlinCompilationConfiguration.kt, > KotlinCompilationConfiguration.kt, KotlinConstants.kt, KotlinConstants.kt, > KotlinConstantsKt-1.class, KotlinConstantsKt-1.class, > KotlinConstantsKt.class, KotlinConstantsKt.class, KotlinDSL-1.class, > KotlinDSL-1.class, KotlinDSL.class, KotlinDSL.class, KotlinDSL.kt, > KotlinDSL.kt, KotlinRoutesBuilderLoader$WhenMappings-1.class, > KotlinRoutesBuilderLoader$WhenMappings-1.class, > KotlinRoutesBuilderLoader$WhenMappings.class, > KotlinRoutesBuilderLoader$WhenMappings.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1-1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1-1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1-1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1-1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1.class, > KotlinRoutesBuilderLoader-1.class, KotlinRoutesBuilderLoader-1.class, > KotlinRoutesBuilderLoader.class, KotlinRoutesBuilderLoader.class, > KotlinRoutesBuilderLoader.kt, KotlinRoutesBuilderLoader.kt, > KotlinRoutesBuilderLoaderTest.class, KotlinRoutesBuilderLoaderTest.class, > KotlinRoutesBuilderLoaderTest.kt, KotlinRoutesBuilderLoaderTest.kt, > LICENSE.txt, LICENSE.txt, LanguagesConfiguration-1.class, > LanguagesConfiguration-1.class, LanguagesConfiguration.class, > LanguagesConfiguration.class, LanguagesConfiguration.kt, > LanguagesConfiguration.kt, MANIFEST.MF, MANIFEST.MF, MyBean.class, > MyBean.class, MyBean.kt, MyBean.kt, NOTICE.txt, NOTICE.txt, > RegistryConfiguration-1.class, RegistryConfiguration-1.class, > RegistryConfiguration.class, RegistryConfiguration.kt, > RegistryConfiguration.kt, RestConfiguration-1.class, RestConfiguration.class, > RestConfiguration.kt, RestConfiguration.kt, RestVerbConfiguration-1.class, > RestVerbConfiguration.class, RestVerbConfiguration.class, > RestVerbConfiguration.kt, RestVerbConfiguration.kt, > inline-functions.tab.keystream, inline-functions.tab.keystream, > inline-functions.tab.keystream.len, inline-functions.tab.keystream.len, > inline-functions.tab.len, inline-functions.tab.len, > inline-functions.tab.values.at, inline-functions.tab.values.at, > inline-functions.tab_i.len, inline-functions.tab_i.len, > internal-name-to-source.tab, internal-name-to-source.tab, > internal-name-to-source.tab.keystream, internal-name-to-source.tab.keystream, > internal-name-to-source.tab.keystream.len, > internal-name-to-source.tab.keystream.len, internal-name-to-source.tab.len, > internal-name-to-source.tab.len, internal-name-to-source.tab.values.at, > internal-name-to-source.tab.values.at, internal-name-to-source.tab_i, > internal-name-to-source.tab_i, internal-name-to-source.tab_i.len, > internal-name-to-source.tab_i.len, jandex.idx, jandex.idx, kotlin-dsl-1.json, > kotlin-dsl-1.json, kotlin-dsl.adoc, kotlin-dsl.adoc, kotlin-dsl.json, > kotlin-dsl.json, kts, kts, kts-1, kts-1, last-build.bin, last-build.bin, > log4j2-test-1.properties, log4j2-test-1.properties, log4j2-test.properties, > log4j2-test.properties, lookups.tab, lookups.tab, lookups.tab.keystream, > lookups.tab.keystream, lookups.tab.keystream.len,
[jira] [Updated] (CAMEL-18606) task to remove attachments from CAMEL-18603
[ https://issues.apache.org/jira/browse/CAMEL-18606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek updated CAMEL-18606: - Attachment: subtypes.tab.len > task to remove attachments from CAMEL-18603 > --- > > Key: CAMEL-18606 > URL: https://issues.apache.org/jira/browse/CAMEL-18606 > Project: Camel > Issue Type: Task >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Attachments: KotlinCompilationConfiguration$1$1-1.class, > KotlinCompilationConfiguration$1$1-1.class, > KotlinCompilationConfiguration$1$1.class, > KotlinCompilationConfiguration$1$1.class, > KotlinCompilationConfiguration$1$2-1.class, > KotlinCompilationConfiguration$1$2-1.class, > KotlinCompilationConfiguration$1$2.class, > KotlinCompilationConfiguration$1$2.class, > KotlinCompilationConfiguration$1-1.class, > KotlinCompilationConfiguration$1-1.class, > KotlinCompilationConfiguration$1.class, > KotlinCompilationConfiguration$1.class, > KotlinCompilationConfiguration-1.class, > KotlinCompilationConfiguration-1.class, KotlinCompilationConfiguration.class, > KotlinCompilationConfiguration.class, KotlinCompilationConfiguration.kt, > KotlinCompilationConfiguration.kt, KotlinConstants.kt, KotlinConstants.kt, > KotlinConstantsKt-1.class, KotlinConstantsKt-1.class, > KotlinConstantsKt.class, KotlinConstantsKt.class, KotlinDSL-1.class, > KotlinDSL-1.class, KotlinDSL.class, KotlinDSL.class, KotlinDSL.kt, > KotlinDSL.kt, KotlinRoutesBuilderLoader$WhenMappings-1.class, > KotlinRoutesBuilderLoader$WhenMappings-1.class, > KotlinRoutesBuilderLoader$WhenMappings.class, > KotlinRoutesBuilderLoader$WhenMappings.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1-1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1-1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1.class, > > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$$inlined$createJvmCompilationConfigurationFromTemplate$default$1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1-1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1-1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1.class, > KotlinRoutesBuilderLoader$doLoadEndpointRouteBuilder$result$1.class, > KotlinRoutesBuilderLoader-1.class, KotlinRoutesBuilderLoader-1.class, > KotlinRoutesBuilderLoader.class, KotlinRoutesBuilderLoader.class, > KotlinRoutesBuilderLoader.kt, KotlinRoutesBuilderLoader.kt, > KotlinRoutesBuilderLoaderTest.class, KotlinRoutesBuilderLoaderTest.class, > KotlinRoutesBuilderLoaderTest.kt, KotlinRoutesBuilderLoaderTest.kt, > LICENSE.txt, LICENSE.txt, LanguagesConfiguration-1.class, > LanguagesConfiguration-1.class, LanguagesConfiguration.class, > LanguagesConfiguration.class, LanguagesConfiguration.kt, > LanguagesConfiguration.kt, MANIFEST.MF, MANIFEST.MF, MyBean.class, > MyBean.class, MyBean.kt, MyBean.kt, NOTICE.txt, NOTICE.txt, > RegistryConfiguration-1.class, RegistryConfiguration-1.class, > RegistryConfiguration.class, RegistryConfiguration.kt, > RegistryConfiguration.kt, RestConfiguration-1.class, RestConfiguration.class, > RestConfiguration.kt, RestConfiguration.kt, RestVerbConfiguration-1.class, > RestVerbConfiguration.class, RestVerbConfiguration.class, > RestVerbConfiguration.kt, RestVerbConfiguration.kt, > inline-functions.tab.keystream, inline-functions.tab.keystream, > inline-functions.tab.keystream.len, inline-functions.tab.keystream.len, > inline-functions.tab.len, inline-functions.tab.len, > inline-functions.tab.values.at, inline-functions.tab.values.at, > inline-functions.tab_i.len, inline-functions.tab_i.len, > internal-name-to-source.tab, internal-name-to-source.tab, > internal-name-to-source.tab.keystream, internal-name-to-source.tab.keystream, > internal-name-to-source.tab.keystream.len, > internal-name-to-source.tab.keystream.len, internal-name-to-source.tab.len, > internal-name-to-source.tab.len, internal-name-to-source.tab.values.at, > internal-name-to-source.tab.values.at, internal-name-to-source.tab_i, > internal-name-to-source.tab_i, internal-name-to-source.tab_i.len, > internal-name-to-source.tab_i.len, jandex.idx, jandex.idx, kotlin-dsl-1.json, > kotlin-dsl-1.json, kotlin-dsl.adoc, kotlin-dsl.adoc, kotlin-dsl.json, > kotlin-dsl.json, kts, kts, kts-1, kts-1, last-build.bin, last-build.bin, > log4j2-test-1.properties, log4j2-test-1.properties, log4j2-test.properties, > log4j2-test.properties, lookups.tab, lookups.tab, lookups.tab.keystream, > lookups.tab.keystream, lookups.tab.keystream.len,
[jira] [Updated] (CAMEL-18603) Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
[
https://issues.apache.org/jira/browse/CAMEL-18603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated CAMEL-18603:
-
Attachment: (was: KotlinCompilationConfiguration$1.class)
> Camel-Jbang: When using aws-ddb-sink Kamelet dependency are not resolved
>
>
> Key: CAMEL-18603
> URL: https://issues.apache.org/jira/browse/CAMEL-18603
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.19.0
>Reporter: Andrea Cosentino
>Priority: Major
> Fix For: 3.20.0
>
>
> If you have a route like:
> {code:java}
> # camel-k: dependency=mvn:software.amazon.awssdk:dynamodb:2.17.290
> - route:
> from:
> uri: "kamelet:kafka-not-secured-source"
> parameters:
> bootstrapServers: localhost:9092
> topic: ddb-topic
> steps:
> - to:
> uri: "kamelet:aws-ddb-sink"
> parameters:
> accessKey: access
> secretKey: sec
> region: reg
> table: "test"
> {code}
> Then camel-jbang will fail with
> {code:java}
> Caused by: java.lang.ClassNotFoundException:
> software.amazon.awssdk.services.dynamodb.model.AttributeValue
> 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)
> ... 44 more
> {code}
> the command is: jbang run --fresh -Dcamel.jbang.version=3.19.0
> camel@apache/camel run kafka-source-ddb.yaml
> This will fail with 3.20.0-SNAPSHOT too and by using --deps from cli
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
