[jira] [Resolved] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20911.
-
Resolution: Fixed
Okay I added workaround in camel-jbang. Christoph if you rebuild code then it
should work for you now as well.
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
[jira] [Updated] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20911:
Fix Version/s: 4.7.0
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
> Fix For: 4.7.0
>
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycl
[jira] [Reopened] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reopened CAMEL-20911:
-
Assignee: Claus Ibsen
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.7.0
>
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:7
[jira] [Commented] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860068#comment-17860068
]
Claus Ibsen commented on CAMEL-20911:
-
Because CEQ 3.12 missed this fix, then lets try to add the workaround into
camel-jbang so it would work nicely OOTB
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle
[jira] [Resolved] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20921. - Resolution: Fixed > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4, 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860067#comment-17860067 ] Claus Ibsen commented on CAMEL-20921: - Thanks for reporting and the unit test > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4, 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20921: Fix Version/s: 4.4.4 (was: 4.4.3) > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.4, 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20921: Fix Version/s: 4.4.3 > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.3, 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20921: --- Assignee: Claus Ibsen > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
[ https://issues.apache.org/jira/browse/CAMEL-20921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20921: Fix Version/s: 4.7.0 > Route configuration is not loaded on a Camel application XML file > - > > Key: CAMEL-20921 > URL: https://issues.apache.org/jira/browse/CAMEL-20921 > Project: Camel > Issue Type: Bug > Components: dsl >Affects Versions: 4.0.3, 4.4.2 >Reporter: Adriano Machado >Priority: Major > Fix For: 4.7.0 > > Attachments: route-config-test.diff > > > Route configurations are not loaded if they are being loaded from an XML file > that uses the `camel` root tag. > > Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860054#comment-17860054
]
kangjian edited comment on CAMEL-20907 at 6/26/24 3:02 AM:
---
Hi [~davsclaus] , sorry, the 3.22.x version is no problem, it's the reason for
my code, I found
jira[CAMEL-19675|https://issues.apache.org/jira/browse/CAMEL-19675] to fix this
bug.
Thank you very much for your help.
was (Author: JIRAUSER305880):
Hi [~davsclaus] , sorry, the 3.22.x version is no problem, it's the reason for
my code, I found jiraCAMEL-19675 to fix this bug.
Thank you very much for your help.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.x
>
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860054#comment-17860054
]
kangjian edited comment on CAMEL-20907 at 6/26/24 3:02 AM:
---
Hi [~davsclaus] , sorry, the 3.22.x version is no problem, it's the reason for
my code, I found jiraCAMEL-19675 to fix this bug.
Thank you very much for your help.
was (Author: JIRAUSER305880):
Hi [~davsclaus] , sorry, the 3.22.x version is no problem, it's the reason for
my code, I found
jira[[CAMEL-19675|https://issues.apache.org/jira/browse/CAMEL-19675]] to fix
this bug.
Thank you very much for your help.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.x
>
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860054#comment-17860054
]
kangjian commented on CAMEL-20907:
--
Hi [~davsclaus] , sorry, the 3.22.x version is no problem, it's the reason for
my code, I found
jira[[CAMEL-19675|https://issues.apache.org/jira/browse/CAMEL-19675]] to fix
this bug.
Thank you very much for your help.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.x
>
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20921) Route configuration is not loaded on a Camel application XML file
Adriano Machado created CAMEL-20921: --- Summary: Route configuration is not loaded on a Camel application XML file Key: CAMEL-20921 URL: https://issues.apache.org/jira/browse/CAMEL-20921 Project: Camel Issue Type: Bug Components: dsl Affects Versions: 4.4.2, 4.0.3 Reporter: Adriano Machado Attachments: route-config-test.diff Route configurations are not loaded if they are being loaded from an XML file that uses the `camel` root tag. Please see the attached diff with a failing test. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20919) Introduce Producer based Health for any SFTPs
[ https://issues.apache.org/jira/browse/CAMEL-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adityakrishnan updated CAMEL-20919: --- Issue Type: Task (was: New Feature) > Introduce Producer based Health for any SFTPs > - > > Key: CAMEL-20919 > URL: https://issues.apache.org/jira/browse/CAMEL-20919 > Project: Camel > Issue Type: Task > Components: camel-sftp, camel-spring-boot > Environment: Camel Springboot > Camel SFTP >Reporter: Adityakrishnan >Priority: Major > Labels: features > Fix For: Future > > Original Estimate: 336h > Remaining Estimate: 336h > > Producer based SFTP Health is not available for regular SFTPs, it is only > accessible by some components (like AWS and Kafka). This has been a need from > some time in work-spaces. > When SFTPs have inconsistent down-times Observability and Monitoring comes > handy for all those who uses Apache Camel. This Producer based Health Check > should also be included in regular SFTPs. > Consumer based and Producer based health check and alerting can prevent an > outage before it occurs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond updated CAMEL-20920:
Description:
I load XML routes from String as follows:
{code:java}
// Create resource from String
String route = "\n" +
" \n" +
" \n" +
"\n" +
"XYZ\n" +
"\n" +
"";
Resource resource = ResourceHelper.fromString("dummy.xml", route);
// Load the routes
RoutesLoader loader = PluginHelper.getRoutesLoader(context);
loader.updateRoutes(resource); {code}
In the above code example, I created the resource from String using the
ResourceHelper class:
{code:java}
Resource resource = ResourceHelper.fromString("dummy.xml", route);
{code}
The _fromString_ method has two parameters "location" and "content". As a
String doesn't really have a location I just use "dummy.xml" or something with
an ID like this "123456.xml".
This works with correct code and when the content has a mistake like invalid
XML code, it returns an error.
This is as expected, however when loading the route again with the correct XML
Code with the same location parameter the loading fails. The loader still
returns the previous error. When the location is changed to another name to
route loads correctly.
{color:#cc7832} {color}
was:
I load XML routes from String as follows:
{code:java}
// Create resource from String
String route = "\n" +
" \n" +
" \n" +
"\n" +
"XYZ\n" +
"\n" +
"";
Resource resource = ResourceHelper.fromString("dummy.xml", route);
// Load the routes
RoutesLoader loader = PluginHelper.getRoutesLoader(context);
loader.updateRoutes(resource); {code}
{color:#cc7832}
{color}In the above code example, I created the resource from String using the
ResourceHelper class:
{code:java}
Resource resource = ResourceHelper.fromString("dummy.xml", route);
{code}
The fromString method has two parameters "location" and "content". As a String
doesn't really have a location I just use "dummy.xml" or some ID like this
"123456.xml".
This works with correct code and when the content has a mistake like invalid
XML code, it returns an error.
This is as expected, however when loading the route again with the correct XML
Code with the same location parameter the loading fails. The loader still
returns the previous error. When the location is changed to another name to
route loads correctly.
{color:#cc7832}
{color}
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Priority: Minor
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> In the above code example, I created the resource from String using the
> ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The _fromString_ method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or something
> with an ID like this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832} {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859967#comment-17859967
]
Raymond commented on CAMEL-20920:
-
Add a reproducer that reproduces the behavior as described in the issue.
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Priority: Minor
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> {color:#cc7832}
> {color}In the above code example, I created the resource from String using
> the ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The fromString method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or some ID like
> this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832}
> {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
[
https://issues.apache.org/jira/browse/CAMEL-20920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond updated CAMEL-20920:
Attachment: routeloader.zip
> RouteLoader: Can't load a valid route with the same location after a previous
> load error
>
>
> Key: CAMEL-20920
> URL: https://issues.apache.org/jira/browse/CAMEL-20920
> Project: Camel
> Issue Type: Bug
> Components: camel-core
>Affects Versions: 4.6.0
>Reporter: Raymond
>Priority: Minor
> Attachments: routeloader.zip
>
>
> I load XML routes from String as follows:
> {code:java}
> // Create resource from String
> String route = "\n" +
> " \n" +
> " \n" +
> "\n" +
> "XYZ\n" +
> "\n" +
> "";
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> // Load the routes
> RoutesLoader loader = PluginHelper.getRoutesLoader(context);
> loader.updateRoutes(resource); {code}
> {color:#cc7832}
> {color}In the above code example, I created the resource from String using
> the ResourceHelper class:
> {code:java}
> Resource resource = ResourceHelper.fromString("dummy.xml", route);
> {code}
> The fromString method has two parameters "location" and "content". As a
> String doesn't really have a location I just use "dummy.xml" or some ID like
> this "123456.xml".
> This works with correct code and when the content has a mistake like invalid
> XML code, it returns an error.
> This is as expected, however when loading the route again with the correct
> XML Code with the same location parameter the loading fails. The loader still
> returns the previous error. When the location is changed to another name to
> route loads correctly.
>
> {color:#cc7832}
> {color}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20920) RouteLoader: Can't load a valid route with the same location after a previous load error
Raymond created CAMEL-20920:
---
Summary: RouteLoader: Can't load a valid route with the same
location after a previous load error
Key: CAMEL-20920
URL: https://issues.apache.org/jira/browse/CAMEL-20920
Project: Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 4.6.0
Reporter: Raymond
Attachments: routeloader.zip
I load XML routes from String as follows:
{code:java}
// Create resource from String
String route = "\n" +
" \n" +
" \n" +
"\n" +
"XYZ\n" +
"\n" +
"";
Resource resource = ResourceHelper.fromString("dummy.xml", route);
// Load the routes
RoutesLoader loader = PluginHelper.getRoutesLoader(context);
loader.updateRoutes(resource); {code}
{color:#cc7832}
{color}In the above code example, I created the resource from String using the
ResourceHelper class:
{code:java}
Resource resource = ResourceHelper.fromString("dummy.xml", route);
{code}
The fromString method has two parameters "location" and "content". As a String
doesn't really have a location I just use "dummy.xml" or some ID like this
"123456.xml".
This works with correct code and when the content has a mistake like invalid
XML code, it returns an error.
This is as expected, however when loading the route again with the correct XML
Code with the same location parameter the loading fails. The loader still
returns the previous error. When the location is changed to another name to
route loads correctly.
{color:#cc7832}
{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20919) Introduce Producer based Health for any SFTPs
[ https://issues.apache.org/jira/browse/CAMEL-20919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adityakrishnan updated CAMEL-20919: --- Environment: Camel Springboot Camel SFTP was: Camel Springboot Camel SFTP2 > Introduce Producer based Health for any SFTPs > - > > Key: CAMEL-20919 > URL: https://issues.apache.org/jira/browse/CAMEL-20919 > Project: Camel > Issue Type: New Feature > Components: camel-sftp, camel-spring-boot > Environment: Camel Springboot > Camel SFTP >Reporter: Adityakrishnan >Priority: Major > Labels: features > Fix For: Future > > Original Estimate: 336h > Remaining Estimate: 336h > > Producer based SFTP Health is not available for regular SFTPs, it is only > accessible by some components (like AWS and Kafka). This has been a need from > some time in work-spaces. > When SFTPs have inconsistent down-times Observability and Monitoring comes > handy for all those who uses Apache Camel. This Producer based Health Check > should also be included in regular SFTPs. > Consumer based and Producer based health check and alerting can prevent an > outage before it occurs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20919) Introduce Producer based Health for any SFTPs
Adityakrishnan created CAMEL-20919: -- Summary: Introduce Producer based Health for any SFTPs Key: CAMEL-20919 URL: https://issues.apache.org/jira/browse/CAMEL-20919 Project: Camel Issue Type: New Feature Components: camel-sftp, camel-spring-boot Environment: Camel Springboot Camel SFTP2 Reporter: Adityakrishnan Fix For: Future Producer based SFTP Health is not available for regular SFTPs, it is only accessible by some components (like AWS and Kafka). This has been a need from some time in work-spaces. When SFTPs have inconsistent down-times Observability and Monitoring comes handy for all those who uses Apache Camel. This Producer based Health Check should also be included in regular SFTPs. Consumer based and Producer based health check and alerting can prevent an outage before it occurs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
[ https://issues.apache.org/jira/browse/CAMEL-20722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859925#comment-17859925 ] Jang-Vijay Singh commented on CAMEL-20722: -- *KafkaBreakOnFirstErrorSeekIssueIT* has now also been working on both main and ppc64le after the last merge > camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs > --- > > Key: CAMEL-20722 > URL: https://issues.apache.org/jira/browse/CAMEL-20722 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Assignee: Jang-Vijay Singh >Priority: Major > Labels: help-wanted > Fix For: 4.7.0 > > Attachments: Stable-tests_2024-06-13.txt, build-log.txt > > > All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the > CI. They fail often, sometimes in multiple archs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20918) Salesforce component does not resubscribe after exception
Bartosz Popiela created CAMEL-20918: --- Summary: Salesforce component does not resubscribe after exception Key: CAMEL-20918 URL: https://issues.apache.org/jira/browse/CAMEL-20918 Project: Camel Issue Type: Bug Components: camel-salesforce Affects Versions: 4.6.0, 4.4.2, 3.22.2 Reporter: Bartosz Popiela TODO will be updated -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20907.
-
Fix Version/s: 4.x
Assignee: Claus Ibsen
Resolution: Information Provided
It works in Camel v4
[https://github.com/apache/camel/blob/main/components/camel-mail/src/test/java/org/apache/camel/component/mail/MailAttachmentPollEnrichTest.java]
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.x
>
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20917) camel-jbang: Camel Jbang is unable to load external plugins
Otavio Rodolfo Piske created CAMEL-20917:
Summary: camel-jbang: Camel Jbang is unable to load external
plugins
Key: CAMEL-20917
URL: https://issues.apache.org/jira/browse/CAMEL-20917
Project: Camel
Issue Type: Task
Components: camel-jbang
Affects Versions: 4.7.0
Reporter: Otavio Rodolfo Piske
Assignee: Otavio Rodolfo Piske
Fix For: 4.7.0
When trying to load a plugin defined as:
{code:xml}
org.apache.camel.jbang.ai
camel-jbang-plugin-explain
1.0.0-SNAPSHOT
{code}
Then adding it to JBang as:
{code:shell}
jbang -Dcamel.jbang.version=4.7.0-SNAPSHOT camel@apache/camel plugin add -g
org.apache.camel.jbang.ai -a camel-jbang-plugin-explain -v 1.0.0-SNAPSHOT -d
"Explain things using AI" explain
{code}
Then, JBang fails to load the plugin with the following error:
{code:java}
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not
find artifact org.apache.camel:camel-jbang-plugin-explain:jar:4.7.0-SNAPSHOT in
apache-snapshot (https://repository.apache.org/snapshots)
{code}
This happens because the group and version are hard-coded in the PluginHelper
class.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers add an example
[ https://issues.apache.org/jira/browse/CAMEL-20914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20914: - Summary: Camel-AWS-Kinesis: KCL Consumers add an example (was: Camel-AWS-Kinesis: KCL Consumers and an example) > Camel-AWS-Kinesis: KCL Consumers add an example > --- > > Key: CAMEL-20914 > URL: https://issues.apache.org/jira/browse/CAMEL-20914 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20916) Camel-AWS-Kinesis: KCL Consumers, add documentation
Andrea Cosentino created CAMEL-20916: Summary: Camel-AWS-Kinesis: KCL Consumers, add documentation Key: CAMEL-20916 URL: https://issues.apache.org/jira/browse/CAMEL-20916 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.7.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20915) test-infra: automate checking for container upgrades
[
https://issues.apache.org/jira/browse/CAMEL-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859871#comment-17859871
]
Aurélien Pupier commented on CAMEL-20915:
-
I think we can try to follow the convention from github depdenabot which will
provide automatic PR for the upgrade then
https://github.blog/changelog/2024-01-24-dependabot-version-updates-support-devcontainers/
> test-infra: automate checking for container upgrades
>
>
> Key: CAMEL-20915
> URL: https://issues.apache.org/jira/browse/CAMEL-20915
> Project: Camel
> Issue Type: Task
> Components: test-infra
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> We use a lot of containers as part of our tests. With time, they become
> outdated and we have to manually check for upgrades.
> This tasks is to create a script to automate checking for new versions of the
> containers.
> You can find all the containers used in Camel by running the following
> command:
> {code:java}
> find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} |
> grep container | cut -d = -f 2 " \;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20915) test-infra: automate checking for container upgrades
[
https://issues.apache.org/jira/browse/CAMEL-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20915:
-
Description:
We use a lot of containers as part of our tests. With time, they become
outdated and we have to manually check for upgrades.
This tasks is to create a script to automate checking for new versions of the
containers.
You can find all the containers used in Camel by running the following command:
find . -iname 'container.properties' -ipath '**src**' -exec sh -c "cat {} |
grep container | cut -d = -f 2 " \;
was:
We use a lot of containers as part of our tests. With time, they become
outdated and we have to manually check for upgrades.
This tasks is to create a script to automate checking for new versions of the
containers.
You can find all the containers used in Camel by running the following command:
find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} | grep
container | cut -d = -f 2 " \;
> test-infra: automate checking for container upgrades
>
>
> Key: CAMEL-20915
> URL: https://issues.apache.org/jira/browse/CAMEL-20915
> Project: Camel
> Issue Type: Task
> Components: test-infra
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> We use a lot of containers as part of our tests. With time, they become
> outdated and we have to manually check for upgrades.
> This tasks is to create a script to automate checking for new versions of the
> containers.
> You can find all the containers used in Camel by running the following
> command:
> find . -iname 'container.properties' -ipath '**src**' -exec sh -c "cat {} |
> grep container | cut -d = -f 2 " \;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20915) test-infra: automate checking for container upgrades
[
https://issues.apache.org/jira/browse/CAMEL-20915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-20915:
-
Description:
We use a lot of containers as part of our tests. With time, they become
outdated and we have to manually check for upgrades.
This tasks is to create a script to automate checking for new versions of the
containers.
You can find all the containers used in Camel by running the following command:
{code:java}
find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} | grep
container | cut -d = -f 2 " \;
{code}
was:
We use a lot of containers as part of our tests. With time, they become
outdated and we have to manually check for upgrades.
This tasks is to create a script to automate checking for new versions of the
containers.
You can find all the containers used in Camel by running the following command:
find . -iname 'container.properties' -ipath '**src**' -exec sh -c "cat {} |
grep container | cut -d = -f 2 " \;
> test-infra: automate checking for container upgrades
>
>
> Key: CAMEL-20915
> URL: https://issues.apache.org/jira/browse/CAMEL-20915
> Project: Camel
> Issue Type: Task
> Components: test-infra
>Affects Versions: 4.7.0
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Labels: help-wanted
> Fix For: 4.x
>
>
> We use a lot of containers as part of our tests. With time, they become
> outdated and we have to manually check for upgrades.
> This tasks is to create a script to automate checking for new versions of the
> containers.
> You can find all the containers used in Camel by running the following
> command:
> {code:java}
> find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} |
> grep container | cut -d = -f 2 " \;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20915) test-infra: automate checking for container upgrades
Otavio Rodolfo Piske created CAMEL-20915:
Summary: test-infra: automate checking for container upgrades
Key: CAMEL-20915
URL: https://issues.apache.org/jira/browse/CAMEL-20915
Project: Camel
Issue Type: Task
Components: test-infra
Affects Versions: 4.7.0
Reporter: Otavio Rodolfo Piske
Fix For: 4.x
We use a lot of containers as part of our tests. With time, they become
outdated and we have to manually check for upgrades.
This tasks is to create a script to automate checking for new versions of the
containers.
You can find all the containers used in Camel by running the following command:
find . -iname 'container.properties' -ipath '*src*' -exec sh -c "cat {} | grep
container | cut -d = -f 2 " \;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859858#comment-17859858
]
Claus Ibsen commented on CAMEL-20907:
-
Okay if you can try with latest 4.4.x or 4.6.0 release.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Minor
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859845#comment-17859845
]
Claus Ibsen commented on CAMEL-20911:
-
I think they fixed it by setting a default value, you can do this in
application.properties as workaround or as a --prop value
https://github.com/apache/camel-quarkus/commit/a3338cf3a6c17849c980c1ebbc23dba506d25e83
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleMo
[jira] [Commented] (CAMEL-20907) came-mail - In Poll Enrich EIP, get email attachments are empty
[
https://issues.apache.org/jira/browse/CAMEL-20907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859843#comment-17859843
]
kangjian commented on CAMEL-20907:
--
[~davsclaus] I tried to upgrade to version 3.22.x, but I still can't get the
attachment to the email.
> came-mail - In Poll Enrich EIP, get email attachments are empty
> ---
>
> Key: CAMEL-20907
> URL: https://issues.apache.org/jira/browse/CAMEL-20907
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: kangjian
>Priority: Minor
>
> Let's say I need to wait for an event notification and then pull an
> attachments email like this:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true")
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> // Here attachments is null
> Map attachments = attachmentMessage.getAttachments();
> })
> .end();{code}
>
> Same code, works fine in Camel 3.14.x but doesn't work in Camel 3.18.x.
> After debugging, it was found that in Camel 3.16.x, the implementation of
> DefaultAttachmentMessage.java was upgraded.
> The key point is the CamelAttachmentObjects property in the ExchangeProperty,
> which is placed in the Exchange property in version 3.14.x, and in the
> ExtendedExchange property in version 3.16.x, which results in the loss of the
> CamelAttachmentObjects property between different Exchange.
> Details can be found in the link below line 274:
> [https://github.com/apache/camel/commit/0125a133a11cbdff57d459634bac276c10963387]
> I tried a solution as follows:
> Camel version 3.18.x
> {code:java}
> from("servlet://foo?servletName=MyServlet")
> .loopDoWhile().simple("${exchangeProperty.CamelBatchComplete} == null ||
> ${exchangeProperty.CamelBatchComplete} == false")
> .pollEnrich("imaps://{{mail.server}}?session=#oAuthSession&closeFolder=false&peek=true&folderName={{mail.sub.folder}}&sendEmptyMessageWhenIdle=true",
> ((oldExchange, newExchange) -> {
> // Deliver the attachment to the oldExchange
> oldExchange.setIn(newExchange.getIn(AttachmentMessage.class));
> return oldExchange;
> }))
> .process(exchange -> {
> AttachmentMessage attachmentMessage = exchange.getIn(AttachmentMessage.class);
> Map attachments = attachmentMessage.getAttachments();
> })
> .end(); {code}
> The above can solve the problem of not being able to get attachments, but
> there will be other properties missing.
> Can you help with this? If information is missing, please do not hesitate to
> contact.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859842#comment-17859842
]
Claus Ibsen commented on CAMEL-20911:
-
You can also try with exporting to quarkus 3.10.x version, via
--quarkus-version flag.
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuil
[jira] [Commented] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859841#comment-17859841
]
Claus Ibsen commented on CAMEL-20910:
-
Officially we only use support and use maven wrapper to build (.mvnw dir).
But of course it would be good to see if we can fix this for maven daemon.
[~gnodet] can maybe help.
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Priority: Minor
> Fix For: 4.x
>
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859840#comment-17859840
]
Claus Ibsen edited comment on CAMEL-20911 at 6/25/24 7:41 AM:
--
Yes its a bug/issue in CEQ [~jamesnetherton] is aware of this, and they will
fix in upcoming CEQ releases.
You can set some property as workaround. James can tell more.
was (Author: davsclaus):
Yes its a bug/issue in CEQ [~jamesnetherton] is aware of this
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.ex
[jira] [Commented] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859840#comment-17859840
]
Claus Ibsen commented on CAMEL-20911:
-
Yes its a bug/issue in CEQ [~jamesnetherton] is aware of this
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (Lifec
[jira] [Resolved] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20911.
-
Resolution: Information Provided
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:73)
> at
> org.apache.maven.lifecycle.internal.builde
[jira] [Created] (CAMEL-20914) Camel-AWS-Kinesis: KCL Consumers and an example
Andrea Cosentino created CAMEL-20914: Summary: Camel-AWS-Kinesis: KCL Consumers and an example Key: CAMEL-20914 URL: https://issues.apache.org/jira/browse/CAMEL-20914 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20913) Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients
Andrea Cosentino created CAMEL-20913: Summary: Camel-AWS-Kinesis: KCL Consumers, add support for profile/default/session credentials for Cloudwatch and DynamoDB clients Key: CAMEL-20913 URL: https://issues.apache.org/jira/browse/CAMEL-20913 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20912: - Fix Version/s: 4.x > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
[ https://issues.apache.org/jira/browse/CAMEL-20912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-20912: Assignee: Andrea Cosentino > Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and > DynamoDB Clients > --- > > Key: CAMEL-20912 > URL: https://issues.apache.org/jira/browse/CAMEL-20912 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20912) Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients
Andrea Cosentino created CAMEL-20912: Summary: Camel-AWS-Kinesis: KCL Consumers add parameters for passing Cloudwatch and DynamoDB Clients Key: CAMEL-20912 URL: https://issues.apache.org/jira/browse/CAMEL-20912 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
[
https://issues.apache.org/jira/browse/CAMEL-20911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859830#comment-17859830
]
Christoph Deppisch commented on CAMEL-20911:
This seems to work with Camel 4.6.0 which uses Camel Quarkus 3.10.0. Camel
4.7.0 uses Camel Quarkus 3.11.0 which causes the error
> Maven build failure for Camel JBang exported Quarkus app
>
>
> Key: CAMEL-20911
> URL: https://issues.apache.org/jira/browse/CAMEL-20911
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.7.0
>Reporter: Christoph Deppisch
>Priority: Major
>
> When Camel JBang exports code to a Quarkus Maven application the resulting
> build fails with:
> {noformat}
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source{noformat}
> The code exported is Sample.java:
> {noformat}
> import org.apache.camel.builder.RouteBuilder;
> public class Sample extends RouteBuilder {
> @Override
> public void configure() throws Exception {
> from("timer:tick")
> .log("Hello Camel!");
> }
> }{noformat}
> The Camel JBang command used to export:
> {noformat}
> camel export Sample.java --runtime=quarkus
> --gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
> Camel version: 4.7.0-SNAPSHOT
> The Maven output when calling _mvn package_ on the generated export project:
> {noformat}
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.909 s
> [INFO] Finished at: 2024-06-25T09:03:20+02:00
> [INFO]
>
> [ERROR] Failed to execute goal
> io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
> sample: Failed to build quarkus application: SRCFG00014: The config property
> quarkus.camel.openapi.codegen.model-package is required but it could not be
> found in any config source -> [Help 1]{noformat}
> Maven StackTrace:
> {noformat}
> Caused by: io.quarkus.runtime.configuration.ConfigurationException:
> SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package
> is required but it could not be found in any config source
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
> (BuildTimeConfigurationReader.java:944)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:882)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
> (BuildTimeConfigurationReader.java:923)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
> (BuildTimeConfigurationReader.java:516)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
> (BuildTimeConfigurationReader.java:424)
> at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
> at
> io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
> (BuildTimeConfigurationReader.java:424)
> at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
> (ExtensionLoader.java:140)
> at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
> at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
> (AugmentActionImpl.java:327)
> at
> io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
> (AugmentActionImpl.java:173)
> at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
> at io.quarkus.maven.QuarkusBootstrapMojo.execute
> (QuarkusBootstrapMojo.java:171)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:126)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
> (MojoExecutor.java:328)
> at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
> (MojoExecutor.java:316)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:212)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:174)
> at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
> (MojoExecutor.java:75)
> at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
> (MojoExecutor.java:162)
> at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
> (DefaultMojosExecutionStrategy.java:39)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:159)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:105)
> at
[jira] [Created] (CAMEL-20911) Maven build failure for Camel JBang exported Quarkus app
Christoph Deppisch created CAMEL-20911:
--
Summary: Maven build failure for Camel JBang exported Quarkus app
Key: CAMEL-20911
URL: https://issues.apache.org/jira/browse/CAMEL-20911
Project: Camel
Issue Type: Bug
Components: camel-jbang
Affects Versions: 4.7.0
Reporter: Christoph Deppisch
When Camel JBang exports code to a Quarkus Maven application the resulting
build fails with:
{noformat}
SRCFG00014: The config property quarkus.camel.openapi.codegen.model-package is
required but it could not be found in any config source{noformat}
The code exported is Sample.java:
{noformat}
import org.apache.camel.builder.RouteBuilder;
public class Sample extends RouteBuilder {
@Override
public void configure() throws Exception {
from("timer:tick")
.log("Hello Camel!");
}
}{noformat}
The Camel JBang command used to export:
{noformat}
camel export Sample.java --runtime=quarkus
--gav=org.apache.camel:sample:1.0-SNAPSHOT --dir sample{noformat}
Camel version: 4.7.0-SNAPSHOT
The Maven output when calling _mvn package_ on the generated export project:
{noformat}
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2.909 s
[INFO] Finished at: 2024-06-25T09:03:20+02:00
[INFO]
[ERROR] Failed to execute goal
io.quarkus.platform:quarkus-maven-plugin:3.11.3:build (default) on project
sample: Failed to build quarkus application: SRCFG00014: The config property
quarkus.camel.openapi.codegen.model-package is required but it could not be
found in any config source -> [Help 1]{noformat}
Maven StackTrace:
{noformat}
Caused by: io.quarkus.runtime.configuration.ConfigurationException: SRCFG00014:
The config property quarkus.camel.openapi.codegen.model-package is required but
it could not be found in any config source
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigValue
(BuildTimeConfigurationReader.java:944)
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
(BuildTimeConfigurationReader.java:882)
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.readConfigGroup
(BuildTimeConfigurationReader.java:923)
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader$ReadOperation.run
(BuildTimeConfigurationReader.java:516)
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader.lambda$readConfiguration$0
(BuildTimeConfigurationReader.java:424)
at io.smallrye.config.SecretKeys.doUnlocked (SecretKeys.java:28)
at
io.quarkus.deployment.configuration.BuildTimeConfigurationReader.readConfiguration
(BuildTimeConfigurationReader.java:424)
at io.quarkus.deployment.ExtensionLoader.loadStepsFrom
(ExtensionLoader.java:140)
at io.quarkus.deployment.QuarkusAugmentor.run (QuarkusAugmentor.java:107)
at io.quarkus.runner.bootstrap.AugmentActionImpl.runAugment
(AugmentActionImpl.java:327)
at
io.quarkus.runner.bootstrap.AugmentActionImpl.createProductionApplication
(AugmentActionImpl.java:173)
at io.quarkus.maven.BuildMojo.doExecute (BuildMojo.java:133)
at io.quarkus.maven.QuarkusBootstrapMojo.execute
(QuarkusBootstrapMojo.java:171)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:73)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenC
