[jira] [Resolved] (CAMEL-21578) Avoid "'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing." when exporting openshift project with Camel Jbang

2025-01-13 Thread Jira


 [ 
https://issues.apache.org/jira/browse/CAMEL-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aurélien Pupier resolved CAMEL-21578.
-
Resolution: Fixed

> Avoid "'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing." when exporting 
> openshift project with Camel Jbang
> 
>
> Key: CAMEL-21578
> URL: https://issues.apache.org/jira/browse/CAMEL-21578
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Fix For: 4.10.0
>
>
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel init 
> 'test-from-vscode.camel.yaml'
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel kubernetes run 
> test-from-vscode.camel.yaml --camel-version=4.9.0 --cluster-type=openshift
> {noformat}
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.example.project:test-from-vscode:jar:1.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing. @ line 153, 
> column 21
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-21405) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits

2025-01-13 Thread Gaelle Fournier (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912484#comment-17912484
 ] 

Gaelle Fournier commented on CAMEL-21405:
-

It is no longer relevant.

> camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits
> ---
>
> Key: CAMEL-21405
> URL: https://issues.apache.org/jira/browse/CAMEL-21405
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.x
>Reporter: Gaelle Fournier
>Assignee: Thomas Diesler
>Priority: Minor
>
> In Kubernetes plugin, Ingress trait (service exposure) is only available 
> through the generated kubernetes manifest.
> To leverage quarkus cloud readyness we should add for quarkus runtime cases 
> the use of : 
> [https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes]
>  
> There is a bug on quarkus kubernetes extension that needs to be fixed before 
> this can be done for non "Prefix" type-path route to work : 
> https://github.com/quarkusio/quarkus/issues/43783



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21405) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits

2025-01-13 Thread Gaelle Fournier (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gaelle Fournier resolved CAMEL-21405.
-
Resolution: Won't Do

> camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits
> ---
>
> Key: CAMEL-21405
> URL: https://issues.apache.org/jira/browse/CAMEL-21405
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.x
>Reporter: Gaelle Fournier
>Assignee: Thomas Diesler
>Priority: Minor
>
> In Kubernetes plugin, Ingress trait (service exposure) is only available 
> through the generated kubernetes manifest.
> To leverage quarkus cloud readyness we should add for quarkus runtime cases 
> the use of : 
> [https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes]
>  
> There is a bug on quarkus kubernetes extension that needs to be fixed before 
> this can be done for non "Prefix" type-path route to work : 
> https://github.com/quarkusio/quarkus/issues/43783



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-21612:
---

Assignee: Claus Ibsen

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
> {noformat}
> it is affecting debug functionality in VS Code



--
Thi

[jira] [Updated] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-21612:

Fix Version/s: 4.10.0

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
> {noformat}
> it is affecting debug functiona

[jira] [Created] (CAMEL-21613) Camel-Jbang Kubernetes Plugin: allow to choose image platform options

2025-01-13 Thread Gaelle Fournier (Jira)
Gaelle Fournier created CAMEL-21613:
---

 Summary: Camel-Jbang Kubernetes Plugin: allow to choose image 
platform options
 Key: CAMEL-21613
 URL: https://issues.apache.org/jira/browse/CAMEL-21613
 Project: Camel
  Issue Type: Improvement
  Components: camel-jbang
Reporter: Gaelle Fournier


We should be able to configure for which architecture platform(s) we cant to 
build the container.

 

Currently we build the container image (with docker, JIB or podman) for both 
linux/amd64 and linux/arm64. That mean we need the user to be able to do 
multi-platform build.

While it is available out of the box for JIB (and maybe podman), for docker it 
requires some specific tools like Qemu/buildx. We need to allow the user to 
override the default configuration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-21612.
-
Resolution: Fixed

okay found the bug and fixed for next release

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
>

[jira] [Created] (CAMEL-21617) camel-core - Add doCatch and doFinally to doTry json model

2025-01-13 Thread Claus Ibsen (Jira)
Claus Ibsen created CAMEL-21617:
---

 Summary: camel-core - Add doCatch and doFinally to doTry json model
 Key: CAMEL-21617
 URL: https://issues.apache.org/jira/browse/CAMEL-21617
 Project: Camel
  Issue Type: Task
  Components: camel-core, tooling
Reporter: Claus Ibsen
 Fix For: 4.x


The doTry.json does not include doCatch and doFinally in its json metadata file.

Lets see if we can add them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21615) camel-jbang - Nicer error when export without name or gav

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-21615.
-
Resolution: Fixed

> camel-jbang - Nicer error when export without name or gav
> -
>
> Key: CAMEL-21615
> URL: https://issues.apache.org/jira/browse/CAMEL-21615
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> Avoid this ugly stacktrace, but just report a nice one line error
> ~/workspace/deleteme/xxy ❯ camel export --dir=code --runtime=camel-main
> org.apache.camel.RuntimeCamelException: Failed to resolve project name - 
> please provide --name, --gav or source file
>     at 
> org.apache.camel.dsl.jbang.core.commands.Export.getProjectName(Export.java:180)
>     at org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:61)
>     at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:260)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
>     at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
>     at picocli.CommandLine.access$1500(CommandLine.java:148)
>     at 
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
>     at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
>     at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
>     at 
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
>     at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
>     at picocli.CommandLine.execute(CommandLine.java:2174)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:175)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
>     at main.CamelJBang.main(CamelJBang.java:36)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-21616) camel-main - Route exclude pattern does not work for discovered java classes

2025-01-13 Thread Claus Ibsen (Jira)
Claus Ibsen created CAMEL-21616:
---

 Summary: camel-main - Route exclude pattern does not work for 
discovered java classes
 Key: CAMEL-21616
 URL: https://issues.apache.org/jira/browse/CAMEL-21616
 Project: Camel
  Issue Type: Bug
  Components: camel-main
Affects Versions: 4.9.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 4.10.0


https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/The.20property.20javaRoutesExcludePattern.20doesn't.20seem.20to.20work



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21615) camel-jbang - Nicer error when export without name or gav

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-21615:
---

Assignee: Claus Ibsen

> camel-jbang - Nicer error when export without name or gav
> -
>
> Key: CAMEL-21615
> URL: https://issues.apache.org/jira/browse/CAMEL-21615
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> Avoid this ugly stacktrace, but just report a nice one line error
> ~/workspace/deleteme/xxy ❯ camel export --dir=code --runtime=camel-main
> org.apache.camel.RuntimeCamelException: Failed to resolve project name - 
> please provide --name, --gav or source file
>     at 
> org.apache.camel.dsl.jbang.core.commands.Export.getProjectName(Export.java:180)
>     at org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:61)
>     at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:260)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
>     at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
>     at picocli.CommandLine.access$1500(CommandLine.java:148)
>     at 
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
>     at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
>     at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
>     at 
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
>     at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
>     at picocli.CommandLine.execute(CommandLine.java:2174)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:175)
>     at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
>     at main.CamelJBang.main(CamelJBang.java:36)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21616) camel-main - Route exclude pattern does not work for discovered java classes

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-21616.
-
Resolution: Fixed

> camel-main - Route exclude pattern does not work for discovered java classes
> 
>
> Key: CAMEL-21616
> URL: https://issues.apache.org/jira/browse/CAMEL-21616
> Project: Camel
>  Issue Type: Bug
>  Components: camel-main
>Affects Versions: 4.9.0
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> https://camel.zulipchat.com/#narrow/channel/257298-camel/topic/The.20property.20javaRoutesExcludePattern.20doesn't.20seem.20to.20work



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912552#comment-17912552
 ] 

Claus Ibsen commented on CAMEL-21612:
-

its the local-kamelet-dir option that is buggy 

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Priority: Minor
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
> {noformat}
> it is affecting de

[jira] [Commented] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Jira


[ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912555#comment-17912555
 ] 

Aurélien Pupier commented on CAMEL-21612:
-

effectively without the option it is working with 4.9 too:

{noformat}
jbang '-Dcamel.jbang.version=4.9.0' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_9_0.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug'
2025-01-13 15:35:13.435  INFO 4004631 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
starting
2025-01-13 15:35:13.712  INFO 4004631 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 4004631. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 15:35:18.722  INFO 4004631 --- [   main] 
.main.download.MavenDependencyDownloader : Downloading: 
org.apache.camel:camel-debug:4.9.0 (elapsed: 5s)
2025-01-13 15:35:21.858  INFO 4004631 --- [   main] 
.main.download.MavenDependencyDownloader : Resolved: 
org.apache.camel:camel-debug:4.9.0 (took: 8s136ms)
2025-01-13 15:35:22.090  INFO 4004631 --- [   main] 
org.apache.camel.main.ProfileConfigurer  : The application is starting with 
profile: dev
2025-01-13 15:35:22.732  INFO 4004631 --- [   main] 
he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
2025-01-13 15:35:22.733  INFO 4004631 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR (Enabling 
Camel Debugging)
2025-01-13 15:35:22.739  INFO 4004631 --- [   main] 
mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
2025-01-13 15:35:22.930  INFO 4004631 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
is starting
2025-01-13 15:35:23.196  INFO 4004631 --- [   main] 
upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
(directory: .)
2025-01-13 15:35:23.337  INFO 4004631 --- [gerJMXConnector] 
mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening at: 
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
2025-01-13 15:35:23.478  INFO 4004631 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
2025-01-13 15:35:23.479  INFO 4004631 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
2025-01-13 15:35:23.481  INFO 4004631 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
started in 549ms (build:0ms init:0ms start:549ms boot:9s491ms)
2025-01-13 15:35:23.482  INFO 4004631 --- [   main] 
mel.impl.debugger.DefaultBacklogDebugger : Enabling Camel debugger
{noformat}

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Priority: Minor
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 1

[jira] [Assigned] (CAMEL-21613) Camel-Jbang Kubernetes Plugin: allow to choose image platform options

2025-01-13 Thread Thomas Diesler (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Diesler reassigned CAMEL-21613:
--

Assignee: Thomas Diesler

> Camel-Jbang Kubernetes Plugin: allow to choose image platform options
> -
>
> Key: CAMEL-21613
> URL: https://issues.apache.org/jira/browse/CAMEL-21613
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Reporter: Gaelle Fournier
>Assignee: Thomas Diesler
>Priority: Minor
>
> We should be able to configure for which architecture platform(s) we cant to 
> build the container.
>  
> Currently we build the container image (with docker, JIB or podman) for both 
> linux/amd64 and linux/arm64. That mean we need the user to be able to do 
> multi-platform build.
> While it is available out of the box for JIB (and maybe podman), for docker 
> it requires some specific tools like Qemu/buildx. We need to allow the user 
> to override the default configuration.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CAMEL-21087) camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-21087:

Priority: Minor  (was: Major)

> camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait
> 
>
> Key: CAMEL-21087
> URL: https://issues.apache.org/jira/browse/CAMEL-21087
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-jbang
>Reporter: Christoph Deppisch
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.x
>
>
> The jolokia/prometheus trait seems to be valuable for users. Add them to the 
> Kubernetes plugin for Camel JBang



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Jira


[ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912543#comment-17912543
 ] 

Aurélien Pupier commented on CAMEL-21612:
-

there was no change n the camel-debug module itself between 4.8.0 and 4.9.0 
https://github.com/apache/camel/commits/main/components/camel-debug

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-management
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-w

[jira] [Updated] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Jira


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aurélien Pupier updated CAMEL-21612:

Description: 
working with 4.8.2
{noformat}
jbang '-Dcamel.jbang.version=4.8.2' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_8_2.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 

2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
starting
2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 3939143. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
.main.download.MavenDependencyDownloader : Downloaded: 
org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
central@https://repo1.maven.org/maven2
2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
org.apache.camel.main.ProfileConfigurer  : The application is starting with 
profile: dev
2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR (Enabling 
Camel Debugging)
2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 (test-with-4_8_2) 
is starting
2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
(directory: .)
2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening at: 
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 (test-with-4_8_2) 
started in 398ms (build:0ms init:0ms start:398ms)
{noformat}

no more working with Camel 4.9.0:
{noformat}
jbang '-Dcamel.jbang.version=4.9.0' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_9_0.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 

2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
starting
2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 3936155. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
org.apache.camel.main.ProfileConfigurer  : The application is starting with 
profile: dev
2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
is starting
2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
(directory: .)
2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
started in 526ms (build:0ms init:0ms start:526ms boot:1s639ms)
{noformat}

it is affecting debug functionality in VS Code

  was:
working with 4.8.2
{noformat}
jbang '-Dcamel.jbang.version=4.8.2' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_8_2.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 

2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
starting
2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 3939143. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
.main.download.MavenDependencyDownloader : Dow

[jira] [Updated] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-21612:

Component/s: camel-jbang
 (was: camel-management)

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Priority: Major
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20

[jira] [Updated] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-21612:

Priority: Minor  (was: Major)

> [Regression] Camel JMX debugger is no more activated with 
> org.apache.camel:camel-debug dependency
> -
>
> Key: CAMEL-21612
> URL: https://issues.apache.org/jira/browse/CAMEL-21612
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Priority: Minor
>
> working with 4.8.2
> {noformat}
> jbang '-Dcamel.jbang.version=4.8.2' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_8_2.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
> starting
> 2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3939143. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
> .main.download.MavenDependencyDownloader : Downloaded: 
> org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
> central@https://repo1.maven.org/maven2
> 2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR 
> (Enabling Camel Debugging)
> 2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
> mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
> 2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) is starting
> 2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
> mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening 
> at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
> 2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 
> (test-with-4_8_2) started in 398ms (build:0ms init:0ms start:398ms)
> {noformat}
> no more working with Camel 4.9.0:
> {noformat}
> jbang '-Dcamel.jbang.version=4.9.0' 
> '-Dorg.apache.camel.debugger.suspend=true' camel@apache/camel run 
> test-with-4_9_0.camel.yaml --dev --logging-level=info 
> '--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 
> 2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
> starting
> 2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
> org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 
> 3936155. Started by apupier in /home/apupier/ws/demo/a sub folder
> 2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
> org.apache.camel.main.ProfileConfigurer  : The application is starting with 
> profile: dev
> 2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
> he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
> 2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) is starting
> 2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
> upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
> (directory: .)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
> 2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
> 2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
> e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 
> (test-with-4_9_0) started in 526ms (build:0ms init:0ms start:526ms 
> boot:1s639ms)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21605) camel-jbang - Send command should also be as dev console

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-21605.
-
Resolution: Fixed

> camel-jbang - Send command should also be as dev console
> 
>
> Key: CAMEL-21605
> URL: https://issues.apache.org/jira/browse/CAMEL-21605
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-core, camel-jbang
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.10.0
>
>
> We have a receive dev console, and we should have a new send dev console as 
> well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-21614) Simple expressions execute forever. Thread is RUNNABLE for ever. Issue appears with bean expressions inside simple expressions on SimpleLRUCache

2025-01-13 Thread Jannik Schmeier (Jira)
Jannik Schmeier created CAMEL-21614:
---

 Summary: Simple expressions execute forever. Thread is RUNNABLE 
for ever. Issue appears with bean expressions inside simple expressions on 
SimpleLRUCache
 Key: CAMEL-21614
 URL: https://issues.apache.org/jira/browse/CAMEL-21614
 Project: Camel
  Issue Type: Bug
  Components: camel-core
Affects Versions: 4.8.2
 Environment: jdk-21.0.2+13 (Eclipse Temurin)

Spring Boot 3.3.6

Camel 4.8.2
Reporter: Jannik Schmeier


This is a Follow-Up on this issue: CAMEL-21467

Unfortunately we are still experiencing the same issue with threads getting 
stuck in the state RUNNABLE. It seems like the frequency of the issue has 
greatly decreased though. We have had it twice in about a month.

 

Threaddump:
{noformat}
"Camel (camel-1) thread #4 - timer://my-timer" - Thread t@65
   java.lang.Thread.State: RUNNABLE
    at 
org.apache.camel.support.cache.SimpleLRUCache$OperationContext.close(SimpleLRUCache.java:309)
    at 
org.apache.camel.support.cache.SimpleLRUCache.put(SimpleLRUCache.java:104)
    at 
org.apache.camel.support.cache.SimpleSoftCache.put(SimpleSoftCache.java:114)
    at 
org.apache.camel.component.bean.BeanComponent.addBeanInfoToCache(BeanComponent.java:96)
    at org.apache.camel.component.bean.BeanInfo.(BeanInfo.java:169)
    at 
org.apache.camel.component.bean.ConstantBeanHolder.(ConstantBeanHolder.java:50)
    at 
org.apache.camel.language.bean.BeanExpression.createBeanHolder(BeanExpression.java:303)
    at 
org.apache.camel.language.bean.BeanExpression.init(BeanExpression.java:175)
    at 
org.apache.camel.language.bean.BeanLanguage.createExpression(BeanLanguage.java:148)
    at 
org.apache.camel.language.simple.SimpleExpressionBuilder$KeyedOgnlExpressionAdapter.evaluate(SimpleExpressionBuilder.java:1251)
    at 
org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
    at 
org.apache.camel.support.builder.ExpressionBuilder$62.evaluate(ExpressionBuilder.java:2105)
    at 
org.apache.camel.support.ExpressionAdapter.evaluate(ExpressionAdapter.java:45)
    at org.apache.camel.processor.LogProcessor.process(LogProcessor.java:71)
    at 
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808)
    at 
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
    at 
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:178)
    at 
org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
    at 
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
    at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:102)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:84)
    at 
org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:32)
    at 
org.apache.camel.impl.engine.CamelInternalProcessor.processTransacted(CamelInternalProcessor.java:390)
    at 
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:320)
    at 
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:102)
    at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:208)
    at 
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.doRun(RedeliveryErrorHandler.java:808)
    at 
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.run(RedeliveryErrorHandler.java:714)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.executeFromQueue(DefaultReactiveExecutor.java:240)
    at 
org.apache.camel.impl.engine.DefaultReactiveExecutor.executeFromQueue(DefaultReactiveExecutor.java:77)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.await(DefaultAsyncProcessorAwaitManager.java:95)
    at 
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitMan

[jira] [Commented] (CAMEL-21087) camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait

2025-01-13 Thread Thomas Diesler (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912524#comment-17912524
 ] 

Thomas Diesler commented on CAMEL-21087:


Are we talking about migrating this code 
[https://github.com/tdiesler/camel-k/blob/main/pkg/trait/jolokia.go]
with these docs [https://camel.apache.org/camel-k/next/traits/jolokia.html]
to the java code base, or is the jolokia/prometheus trait something different?

> camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait
> 
>
> Key: CAMEL-21087
> URL: https://issues.apache.org/jira/browse/CAMEL-21087
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-jbang
>Reporter: Christoph Deppisch
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.x
>
>
> The jolokia/prometheus trait seems to be valuable for users. Add them to the 
> Kubernetes plugin for Camel JBang



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-21612) [Regression] Camel JMX debugger is no more activated with org.apache.camel:camel-debug dependency

2025-01-13 Thread Jira
Aurélien Pupier created CAMEL-21612:
---

 Summary: [Regression] Camel JMX debugger is no more activated with 
org.apache.camel:camel-debug dependency
 Key: CAMEL-21612
 URL: https://issues.apache.org/jira/browse/CAMEL-21612
 Project: Camel
  Issue Type: Bug
  Components: camel-management
Affects Versions: 4.9.0
Reporter: Aurélien Pupier


working with 4.8.2
{noformat}
jbang '-Dcamel.jbang.version=4.8.2' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_8_2.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 

2025-01-13 14:54:41.775  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.8.2 is 
starting
2025-01-13 14:54:42.129  INFO 3939143 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 3939143. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 14:54:43.681  INFO 3939143 --- [   main] 
.main.download.MavenDependencyDownloader : Downloaded: 
org.apache.camel:camel-debug:4.8.2 (took: 1s536ms) from: 
central@https://repo1.maven.org/maven2
2025-01-13 14:54:43.907  INFO 3939143 --- [   main] 
org.apache.camel.main.ProfileConfigurer  : The application is starting with 
profile: dev
2025-01-13 14:54:44.575  INFO 3939143 --- [   main] 
he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
2025-01-13 14:54:44.576  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Detected: camel-debug JAR (Enabling 
Camel Debugging)
2025-01-13 14:54:44.587  INFO 3939143 --- [   main] 
mel.impl.debugger.DefaultBacklogDebugger : Waiting for a debugger to attach
2025-01-13 14:54:44.799  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 (test-with-4_8_2) 
is starting
2025-01-13 14:54:44.972  INFO 3939143 --- [   main] 
upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
(directory: .)
2025-01-13 14:54:45.069  INFO 3939143 --- [gerJMXConnector] 
mpl.debugger.DebuggerJmxConnectorService : Debugger JMXConnector listening at: 
service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi/camel
2025-01-13 14:54:45.197  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
2025-01-13 14:54:45.198  INFO 3939143 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.8.2 (test-with-4_8_2) 
started in 398ms (build:0ms init:0ms start:398ms)
{noformat}

no more working with Camel 4.9.0:
{noformat}
jbang '-Dcamel.jbang.version=4.9.0' '-Dorg.apache.camel.debugger.suspend=true' 
camel@apache/camel run test-with-4_9_0.camel.yaml --dev --logging-level=info 
'--dep=org.apache.camel:camel-debug' --local-kamelet-dir=. 

2025-01-13 14:53:15.468  INFO 3936155 --- [   main] 
org.apache.camel.main.MainSupport: Apache Camel (JBang) 4.9.0 is 
starting
2025-01-13 14:53:15.974  INFO 3936155 --- [   main] 
org.apache.camel.main.MainSupport: Using Java 21.0.3 with PID 3936155. 
Started by apupier in /home/apupier/ws/demo/a sub folder
2025-01-13 14:53:16.307  INFO 3936155 --- [   main] 
org.apache.camel.main.ProfileConfigurer  : The application is starting with 
profile: dev
2025-01-13 14:53:16.901  INFO 3936155 --- [   main] 
he.camel.cli.connector.LocalCliConnector : Camel JBang CLI enabled
2025-01-13 14:53:17.114  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
is starting
2025-01-13 14:53:17.402  INFO 3936155 --- [   main] 
upport.FileWatcherResourceReloadStrategy : Live route reloading enabled 
(directory: .)
2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Routes startup (total:1)
2025-01-13 14:53:17.641  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Started route1 (timer://yaml)
2025-01-13 14:53:17.642  INFO 3936155 --- [   main] 
e.camel.impl.engine.AbstractCamelContext : Apache Camel 4.9.0 (test-with-4_9_0) 
started in 526ms (build:0ms init:0ms start:526ms boot:1s639ms)
{noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-21578) Avoid "'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing." when exporting openshift project with Camel Jbang

2025-01-13 Thread Thomas Diesler (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912477#comment-17912477
 ] 

Thomas Diesler commented on CAMEL-21578:


I found these CAMEL-21087, CAMEL-21405 and CAMEL-21442

Anything in particular, you'd like me to look at?

> Avoid "'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing." when exporting 
> openshift project with Camel Jbang
> 
>
> Key: CAMEL-21578
> URL: https://issues.apache.org/jira/browse/CAMEL-21578
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Fix For: 4.10.0
>
>
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel init 
> 'test-from-vscode.camel.yaml'
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel kubernetes run 
> test-from-vscode.camel.yaml --camel-version=4.9.0 --cluster-type=openshift
> {noformat}
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.example.project:test-from-vscode:jar:1.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing. @ line 153, 
> column 21
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21405) camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits

2025-01-13 Thread Thomas Diesler (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Diesler reassigned CAMEL-21405:
--

Assignee: Thomas Diesler

> camel-jbang - Kubernetes plugin - Use quarkus extensions for ingress traits
> ---
>
> Key: CAMEL-21405
> URL: https://issues.apache.org/jira/browse/CAMEL-21405
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.x
>Reporter: Gaelle Fournier
>Assignee: Thomas Diesler
>Priority: Minor
>
> In Kubernetes plugin, Ingress trait (service exposure) is only available 
> through the generated kubernetes manifest.
> To leverage quarkus cloud readyness we should add for quarkus runtime cases 
> the use of : 
> [https://quarkus.io/guides/deploying-to-kubernetes#exposing-your-application-in-kubernetes]
>  
> There is a bug on quarkus kubernetes extension that needs to be fixed before 
> this can be done for non "Prefix" type-path route to work : 
> https://github.com/quarkusio/quarkus/issues/43783



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21442) camel-jbang - export is no more working when a previous run occured with local-kamelet-dir set to current dir

2025-01-13 Thread Thomas Diesler (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Diesler reassigned CAMEL-21442:
--

Assignee: Thomas Diesler

> camel-jbang - export is no more working when a previous run occured with 
> local-kamelet-dir set to current dir
> -
>
> Key: CAMEL-21442
> URL: https://issues.apache.org/jira/browse/CAMEL-21442
> Project: Camel
>  Issue Type: Bug
>  Components: camel-jbang
>Affects Versions: 4.8.1, 4.8.2, 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.10.0
>
> Attachments: example-test-with-xsl-before-export.zip
>
>
> it is a regression introduced in Camel 4.8.1, it is working fine with Camel 
> 4.8.0
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel init 
> 'test.camel.yaml'
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel run test.camel.yaml 
> --dev --logging-level=info --local-kamelet-dir=.
> * jbang '-Dcamel.jbang.version=4.8.1' camel@apache/camel export 
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT
> {noformat}
> Reusing existing run data
> Exporting as Quarkus project to: .
> java.nio.file.NoSuchFileException: 
> .camel-jbang/work/src/main/resources/kamelets/test.camel.yaml
> at 
> java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
> at 
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
> at 
> java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
> at 
> java.base/sun.nio.fs.UnixFileSystem.copyFile(UnixFileSystem.java:668)
> at java.base/sun.nio.fs.UnixFileSystem.copy(UnixFileSystem.java:1060)
> at 
> java.base/sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:300)
> at java.base/java.nio.file.Files.copy(Files.java:1304)
> at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:911)
> at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.safeCopy(ExportBaseCommand.java:888)
> at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.copySourceFiles(ExportBaseCommand.java:581)
> at 
> org.apache.camel.dsl.jbang.core.commands.ExportQuarkus.export(ExportQuarkus.java:105)
> at 
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:150)
> at 
> org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:63)
> at 
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:248)
> at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at 
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at 
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at 
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at 
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> {noformat}
> Using jbang '-Dcamel.jbang.version=4.8.0' camel@apache/camel export 
> --runtime=quarkus --gav=com.acme:myproject:1.0-SNAPSHOT is exporting 
> successfully and then calling mvn quarkus:dev is working fine
> Potential workarounds:
> * delete .camel-jbang folder
> * or remove property`camel.jbang.localKameletDir` in the 
> .camel-jbang/camel-jbang-run.properties



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Comment Edited] (CAMEL-21578) Avoid "'build.plugins.plugin.version' for org.apache.maven.plugins:maven-resources-plugin is missing." when exporting openshift project with Camel Jbang

2025-01-13 Thread Thomas Diesler (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912477#comment-17912477
 ] 

Thomas Diesler edited comment on CAMEL-21578 at 1/13/25 12:08 PM:
--

I found CAMEL-21087, CAMEL-21405 and CAMEL-21442

Anything in particular, you'd like me to look at?


was (Author: tdiesler):
I found these CAMEL-21087, CAMEL-21405 and CAMEL-21442

Anything in particular, you'd like me to look at?

> Avoid "'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing." when exporting 
> openshift project with Camel Jbang
> 
>
> Key: CAMEL-21578
> URL: https://issues.apache.org/jira/browse/CAMEL-21578
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Aurélien Pupier
>Assignee: Aurélien Pupier
>Priority: Minor
> Fix For: 4.10.0
>
>
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel init 
> 'test-from-vscode.camel.yaml'
> jbang '-Dcamel.jbang.version=4.9.0' camel@apache/camel kubernetes run 
> test-from-vscode.camel.yaml --camel-version=4.9.0 --cluster-type=openshift
> {noformat}
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.example.project:test-from-vscode:jar:1.0-SNAPSHOT
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-resources-plugin is missing. @ line 153, 
> column 21
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21087) camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait

2025-01-13 Thread Thomas Diesler (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Thomas Diesler reassigned CAMEL-21087:
--

Assignee: Thomas Diesler

> camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait
> 
>
> Key: CAMEL-21087
> URL: https://issues.apache.org/jira/browse/CAMEL-21087
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-jbang
>Reporter: Christoph Deppisch
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.x
>
>
> The jolokia/prometheus trait seems to be valuable for users. Add them to the 
> Kubernetes plugin for Camel JBang



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (CAMEL-21617) camel-core - Add doCatch and doFinally to doTry json model

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen reassigned CAMEL-21617:
---

Assignee: Claus Ibsen

> camel-core - Add doCatch and doFinally to doTry json model
> --
>
> Key: CAMEL-21617
> URL: https://issues.apache.org/jira/browse/CAMEL-21617
> Project: Camel
>  Issue Type: Task
>  Components: camel-core, tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.x
>
>
> The doTry.json does not include doCatch and doFinally in its json metadata 
> file.
> Lets see if we can add them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (CAMEL-21617) camel-core - Add doCatch and doFinally to doTry json model

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen updated CAMEL-21617:

Fix Version/s: 4.10.0
   (was: 4.x)

> camel-core - Add doCatch and doFinally to doTry json model
> --
>
> Key: CAMEL-21617
> URL: https://issues.apache.org/jira/browse/CAMEL-21617
> Project: Camel
>  Issue Type: Task
>  Components: camel-core, tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> The doTry.json does not include doCatch and doFinally in its json metadata 
> file.
> Lets see if we can add them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Resolved] (CAMEL-21617) camel-core - Add doCatch and doFinally to doTry json model

2025-01-13 Thread Claus Ibsen (Jira)


 [ 
https://issues.apache.org/jira/browse/CAMEL-21617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-21617.
-
Resolution: Fixed

> camel-core - Add doCatch and doFinally to doTry json model
> --
>
> Key: CAMEL-21617
> URL: https://issues.apache.org/jira/browse/CAMEL-21617
> Project: Camel
>  Issue Type: Task
>  Components: camel-core, tooling
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> The doTry.json does not include doCatch and doFinally in its json metadata 
> file.
> Lets see if we can add them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Commented] (CAMEL-21087) camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait

2025-01-13 Thread Gaelle Fournier (Jira)


[ 
https://issues.apache.org/jira/browse/CAMEL-21087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912605#comment-17912605
 ] 

Gaelle Fournier commented on CAMEL-21087:
-

[~tdiesler]  For Jolokia yes, that's probably the idea.

There is also the prometheus trait : 
[https://github.com/tdiesler/camel-k/blob/main/pkg/trait/prometheus.go]

In any case we should probably separate them in two different issues and see if 
how different it should be in the plugin for both of them. From what I remember 
Jolokia involves a java agent in CK. Also for prometheus CK uses PodMonitor but 
there was some discussion about the possibility to use a sidecar.

> camel-jbang: Kubernetes plugin: Add jolokia/prometheus trait
> 
>
> Key: CAMEL-21087
> URL: https://issues.apache.org/jira/browse/CAMEL-21087
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-jbang
>Reporter: Christoph Deppisch
>Assignee: Thomas Diesler
>Priority: Major
> Fix For: 4.x
>
>
> The jolokia/prometheus trait seems to be valuable for users. Add them to the 
> Kubernetes plugin for Camel JBang



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (CAMEL-21615) camel-jbang - Nicer error when export without name or gav

2025-01-13 Thread Claus Ibsen (Jira)
Claus Ibsen created CAMEL-21615:
---

 Summary: camel-jbang - Nicer error when export without name or gav
 Key: CAMEL-21615
 URL: https://issues.apache.org/jira/browse/CAMEL-21615
 Project: Camel
  Issue Type: Improvement
  Components: camel-jbang
Reporter: Claus Ibsen
 Fix For: 4.10.0


Avoid this ugly stacktrace, but just report a nice one line error

~/workspace/deleteme/xxy ❯ camel export --dir=code --runtime=camel-main
org.apache.camel.RuntimeCamelException: Failed to resolve project name - please 
provide --name, --gav or source file
    at 
org.apache.camel.dsl.jbang.core.commands.Export.getProjectName(Export.java:180)
    at org.apache.camel.dsl.jbang.core.commands.Export.export(Export.java:61)
    at 
org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.doCall(ExportBaseCommand.java:260)
    at 
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
    at 
org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
    at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
    at picocli.CommandLine.access$1500(CommandLine.java:148)
    at 
picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
    at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
    at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
    at 
picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
    at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
    at picocli.CommandLine.execute(CommandLine.java:2174)
    at 
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:175)
    at 
org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
    at main.CamelJBang.main(CamelJBang.java:36)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)