[jira] [Resolved] (CAMEL-18132) Some camel-examples fail with 3.17.0
[ https://issues.apache.org/jira/browse/CAMEL-18132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karen Lease resolved CAMEL-18132. - Resolution: Fixed Minor changes to several examples to make them work with 3.17 and 3.18-SNAPSHOT (kamelet-main). > Some camel-examples fail with 3.17.0 > > > Key: CAMEL-18132 > URL: https://issues.apache.org/jira/browse/CAMEL-18132 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.17.0 >Reporter: Karen Lease >Assignee: Karen Lease >Priority: Minor > Fix For: 3.18.0 > > > With Came 3.17.0 the following test cases in camel-examples fail consistently: > * Camel :: Example :: ActiveMQ Artemis :: Large messages > * Camel :: Example :: Resume API :: Common > * Camel :: Example :: Spring :: Pulsar > * Camel :: Example :: Transformer :: Demo > Resume-API had an incorrect package for Resumables: Fixed > Spring-Pulsar fails to use the custom type converter from byte array to int. > This appears to be a regression caused by CAMEL-18104. (commit > f9346ac691e1b58b4bb858deb0a2eb48986141f7). > Artemis test fails with an OutOfMemory error at > org.apache.camel.converter.stream.CachedOutputStream.write. > Transformer-demo failure is related to stream caching on the response body in > combination with validation. The validator reads the stream and doesn't reset > it. The validator does make a copy of the Message but it doesn't copy the > InputStreamCache so it's modified. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18202) camel-mongodb-gridfs - initial delay is not configured correctly
[ https://issues.apache.org/jira/browse/CAMEL-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18202: Issue Type: Bug (was: Task) > camel-mongodb-gridfs - initial delay is not configured correctly > > > Key: CAMEL-18202 > URL: https://issues.apache.org/jira/browse/CAMEL-18202 > Project: Camel > Issue Type: Bug > Components: camel-mongodb-gridfs >Affects Versions: 3.14.3, 3.17.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > The code seems to be incorrectly setting the initial delay: > > [https://github.com/apache/camel/blob/camel-3.17.x/components/camel-mongodb-gridfs/src/main/java/org/apache/camel/component/mongodb/gridfs/GridFsEndpoint.java#L231-L236] > > It is always set to the value of delay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18202) camel-mongodb-gridfs - initial delay is not configured correctly
[ https://issues.apache.org/jira/browse/CAMEL-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18202: Summary: camel-mongodb-gridfs - initial delay is not configured correctly (was: camel-mongodb-gridfs) > camel-mongodb-gridfs - initial delay is not configured correctly > > > Key: CAMEL-18202 > URL: https://issues.apache.org/jira/browse/CAMEL-18202 > Project: Camel > Issue Type: Task > Components: camel-mongodb-gridfs >Affects Versions: 3.14.3, 3.17.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > The code seems to be incorrectly setting the initial delay: > > [https://github.com/apache/camel/blob/camel-3.17.x/components/camel-mongodb-gridfs/src/main/java/org/apache/camel/component/mongodb/gridfs/GridFsEndpoint.java#L231-L236] > > It is always set to the value of delay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18202) camel-mongodb-gridfs - initial delay is not configured correctly
[ https://issues.apache.org/jira/browse/CAMEL-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18202: Priority: Minor (was: Major) > camel-mongodb-gridfs - initial delay is not configured correctly > > > Key: CAMEL-18202 > URL: https://issues.apache.org/jira/browse/CAMEL-18202 > Project: Camel > Issue Type: Bug > Components: camel-mongodb-gridfs >Affects Versions: 3.14.3, 3.17.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 3.14.4, 3.18.0 > > > The code seems to be incorrectly setting the initial delay: > > [https://github.com/apache/camel/blob/camel-3.17.x/components/camel-mongodb-gridfs/src/main/java/org/apache/camel/component/mongodb/gridfs/GridFsEndpoint.java#L231-L236] > > It is always set to the value of delay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18201) Enhance CamelTestSupport with an option to turn off stopping of the context
[ https://issues.apache.org/jira/browse/CAMEL-18201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18201. - Fix Version/s: 3.18.0 Resolution: Fixed > Enhance CamelTestSupport with an option to turn off stopping of the context > --- > > Key: CAMEL-18201 > URL: https://issues.apache.org/jira/browse/CAMEL-18201 > Project: Camel > Issue Type: Improvement > Components: tests >Affects Versions: 3.18.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.18.0 > > > It would be nice to use CamelTestSupport for testing in camel-quarkus for JVM > tests ([ticket|https://github.com/apache/camel-quarkus/issues/3511]). Main > problem is that `CamelContext` can not be restarted in camel-quarkus. If some > kind of a configuration option (for example junit's ConfigurationParameters) > would allow to disable stopping of the context, `CamelTestSupport` kind of > testing could be adapted. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18205) camel-jbang - Export to Quarkus and Spring Boot support Gradle
Claus Ibsen created CAMEL-18205: --- Summary: camel-jbang - Export to Quarkus and Spring Boot support Gradle Key: CAMEL-18205 URL: https://issues.apache.org/jira/browse/CAMEL-18205 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Fix For: 3.x We support only Maven currently. We may want to allow end users to choose gradle instead. Then we also need gradle-wrapper to be included as well. And for camel-main we cannot package as uber-jar and to run the app then we need to find a way for gradle to run a main class project. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18151) camel-jbang - Export to Quarkus and Spring Boot maven projects
[ https://issues.apache.org/jira/browse/CAMEL-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18151. - Resolution: Fixed > camel-jbang - Export to Quarkus and Spring Boot maven projects > -- > > Key: CAMEL-18151 > URL: https://issues.apache.org/jira/browse/CAMEL-18151 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18204) camel-jbang - Export to Spring Boot or Quarkus should lookup GAV in their specific catalogs
Claus Ibsen created CAMEL-18204: --- Summary: camel-jbang - Export to Spring Boot or Quarkus should lookup GAV in their specific catalogs Key: CAMEL-18204 URL: https://issues.apache.org/jira/browse/CAMEL-18204 Project: Camel Issue Type: Improvement Components: camel-jbang Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.0 Today we map 1:1 to a -starter or a camel-quarkus-x dependency. But we should lookup in the catalog to be sure, and if none exists then fallback to vanilla camel (and maybe WARN log about this). -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (CAMEL-18203) camel-kotlin - Upgrade to 1.7.0
[ https://issues.apache.org/jira/browse/CAMEL-18203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18203. - Resolution: Fixed > camel-kotlin - Upgrade to 1.7.0 > --- > > Key: CAMEL-18203 > URL: https://issues.apache.org/jira/browse/CAMEL-18203 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18151) camel-jbang - Export to Quarkus and Spring Boot maven projects
[ https://issues.apache.org/jira/browse/CAMEL-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17544922#comment-17544922 ] Claus Ibsen edited comment on CAMEL-18151 at 6/17/22 1:00 PM: -- TODO: Add option to copy mvn wrapper files *DONE* TODO: Add option to chose maven or gradle TODO: Add option to add 3rd party maven repository to pom *DONE* was (Author: davsclaus): TODO: Add option to copy mvn wrapper files TODO: Add option to chose maven or gradle TODO: Add option to add 3rd party maven repository to pom *DONE* > camel-jbang - Export to Quarkus and Spring Boot maven projects > -- > > Key: CAMEL-18151 > URL: https://issues.apache.org/jira/browse/CAMEL-18151 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18203) camel-kotlin - Upgrade to 1.7.0
Claus Ibsen created CAMEL-18203: --- Summary: camel-kotlin - Upgrade to 1.7.0 Key: CAMEL-18203 URL: https://issues.apache.org/jira/browse/CAMEL-18203 Project: Camel Issue Type: Dependency upgrade Reporter: Claus Ibsen Fix For: 3.18.0 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (CAMEL-18151) camel-jbang - Export to Quarkus and Spring Boot maven projects
[ https://issues.apache.org/jira/browse/CAMEL-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555378#comment-17555378 ] Claus Ibsen edited comment on CAMEL-18151 at 6/17/22 12:36 PM: --- TODO: camel export to read from properties which runtime and gav to use *DONE* was (Author: davsclaus): TODO: camel export to read from properties which runtime and gav to use > camel-jbang - Export to Quarkus and Spring Boot maven projects > -- > > Key: CAMEL-18151 > URL: https://issues.apache.org/jira/browse/CAMEL-18151 > Project: Camel > Issue Type: New Feature > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.0 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (CAMEL-18202) camel-mongodb-gridfs
[ https://issues.apache.org/jira/browse/CAMEL-18202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-18202: Assignee: Otavio Rodolfo Piske > camel-mongodb-gridfs > > > Key: CAMEL-18202 > URL: https://issues.apache.org/jira/browse/CAMEL-18202 > Project: Camel > Issue Type: Task > Components: camel-mongodb-gridfs >Affects Versions: 3.14.3, 3.17.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.14.4, 3.18.0 > > > The code seems to be incorrectly setting the initial delay: > > [https://github.com/apache/camel/blob/camel-3.17.x/components/camel-mongodb-gridfs/src/main/java/org/apache/camel/component/mongodb/gridfs/GridFsEndpoint.java#L231-L236] > > It is always set to the value of delay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18202) camel-mongodb-gridfs
Otavio Rodolfo Piske created CAMEL-18202: Summary: camel-mongodb-gridfs Key: CAMEL-18202 URL: https://issues.apache.org/jira/browse/CAMEL-18202 Project: Camel Issue Type: Task Components: camel-mongodb-gridfs Affects Versions: 3.17.0, 3.14.3 Reporter: Otavio Rodolfo Piske Fix For: 3.14.4, 3.18.0 The code seems to be incorrectly setting the initial delay: [https://github.com/apache/camel/blob/camel-3.17.x/components/camel-mongodb-gridfs/src/main/java/org/apache/camel/component/mongodb/gridfs/GridFsEndpoint.java#L231-L236] It is always set to the value of delay. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (CAMEL-18201) Enhance CamelTestSupport with an option to turn off stopping of the context
[ https://issues.apache.org/jira/browse/CAMEL-18201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Ondrusek updated CAMEL-18201: -- Summary: Enhance CamelTestSupport with an option to turn off stopping of the context (was: Enhance CamelTestSupport to turn off stopping of the context) > Enhance CamelTestSupport with an option to turn off stopping of the context > --- > > Key: CAMEL-18201 > URL: https://issues.apache.org/jira/browse/CAMEL-18201 > Project: Camel > Issue Type: Improvement > Components: tests >Affects Versions: 3.18.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > It would be nice to use CamelTestSupport for testing in camel-quarkus for JVM > tests ([ticket|https://github.com/apache/camel-quarkus/issues/3511]). Main > problem is that `CamelContext` can not be restarted in camel-quarkus. If some > kind of a configuration option (for example junit's ConfigurationParameters) > would allow to disable stopping of the context, `CamelTestSupport` kind of > testing could be adapted. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (CAMEL-18201) Enhance CamelTestSupport to turn off stopping of the context
Jiri Ondrusek created CAMEL-18201: - Summary: Enhance CamelTestSupport to turn off stopping of the context Key: CAMEL-18201 URL: https://issues.apache.org/jira/browse/CAMEL-18201 Project: Camel Issue Type: Improvement Components: tests Affects Versions: 3.18.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek It would be nice to use CamelTestSupport for testing in camel-quarkus for JVM tests ([ticket|https://github.com/apache/camel-quarkus/issues/3511]). Main problem is that `CamelContext` can not be restarted in camel-quarkus. If some kind of a configuration option (for example junit's ConfigurationParameters) would allow to disable stopping of the context, `CamelTestSupport` kind of testing could be adapted. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (CAMEL-18184) camel-karaf - Support JUnit 5 for camel-test-blueprint
[ https://issues.apache.org/jira/browse/CAMEL-18184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555402#comment-17555402 ] Claus Ibsen commented on CAMEL-18184: - You are welcome to look at the archetypes in camel-karaf as it is using the old junit 4 for testing. > camel-karaf - Support JUnit 5 for camel-test-blueprint > -- > > Key: CAMEL-18184 > URL: https://issues.apache.org/jira/browse/CAMEL-18184 > Project: Camel > Issue Type: New Feature > Components: camel-blueprint >Reporter: Rastislav Papp >Priority: Minor > Fix For: 3.18.0 > > > camel-test-blueprint module does not have a junit 5 variant. It is just 1 > class, and the change is very small (mostly switching to camel-test-junit5 > and changing some imports). I'll create a PR. -- This message was sent by Atlassian Jira (v8.20.7#820007)
