[jira] [Reopened] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reopened CAMEL-20184: - > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-20184. --- Resolution: Information Provided > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-19788) camel-karaf - Simplify BlueprintCamelStateService getState calls
[ https://issues.apache.org/jira/browse/CAMEL-19788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-19788. --- Resolution: Information Provided > camel-karaf - Simplify BlueprintCamelStateService getState calls > > > Key: CAMEL-19788 > URL: https://issues.apache.org/jira/browse/CAMEL-19788 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: Jan Filipski >Priority: Minor > > Current implementation of BlueprintCamelStateService iterates over map of > states to build list of CamelContext states. > Component key of map (bundleId concatenated with contextId) is not necessary, > because BlueprintCamelStateService can be only used in context of one bundle > (passed in bundleContext). So camel contextId can be used as a key. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-17600) Add camel-azure-servicebus feature
[ https://issues.apache.org/jira/browse/CAMEL-17600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-17600. --- Resolution: Information Provided Report on github instead https://github.com/apache/camel-karaf > Add camel-azure-servicebus feature > -- > > Key: CAMEL-17600 > URL: https://issues.apache.org/jira/browse/CAMEL-17600 > Project: Camel > Issue Type: Task > Components: camel-karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19788) camel-karaf - Simplify BlueprintCamelStateService getState calls
[ https://issues.apache.org/jira/browse/CAMEL-19788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842131#comment-17842131 ] Claus Ibsen commented on CAMEL-19788: - Report on github instead https://github.com/apache/camel-karaf > camel-karaf - Simplify BlueprintCamelStateService getState calls > > > Key: CAMEL-19788 > URL: https://issues.apache.org/jira/browse/CAMEL-19788 > Project: Camel > Issue Type: Improvement > Components: camel-karaf >Reporter: Jan Filipski >Priority: Minor > > Current implementation of BlueprintCamelStateService iterates over map of > states to build list of CamelContext states. > Component key of map (bundleId concatenated with contextId) is not necessary, > because BlueprintCamelStateService can be only used in context of one bundle > (passed in bundleContext). So camel contextId can be used as a key. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (CAMEL-20184) OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing adding routes
[ https://issues.apache.org/jira/browse/CAMEL-20184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen closed CAMEL-20184. --- Resolution: Fixed Report on github instead https://github.com/apache/camel-karaf > OsgiDefaultCamelContext calls init() rather than build() in ctor, preventing > adding routes > -- > > Key: CAMEL-20184 > URL: https://issues.apache.org/jira/browse/CAMEL-20184 > Project: Camel > Issue Type: Bug > Components: camel-karaf >Affects Versions: 3.14.10 >Reporter: Paul McCulloch >Priority: Minor > > The call to init() was added in 3.1 with the comment "OsgiDefaultCamelContext > should init like camel-blueprint does" > (https://github.com/apache/camel/commit/a1c4b82a31108cd23409d0ee6ca4edc5b809b291) > At that time that was the case. However in 3.2 the Blueprint context was > changed to use build() > (https://github.com/apache/camel-karaf/commit/bb1f5042042fbb3e122cb533eddbc3207c3d8efe) > No equaivalent change was made to OsgiDefaultCamelContext. > The symptoms are that routes dont't get added to the context in some > circumstances. In my case I was trying to use a local copy of > https://github.com/apache/camel/blob/camel-2.x/components/camel-scr/src/main/java/org/apache/camel/scr/AbstractCamelRunner.java > too migrate a 2.x project to 3.x. > I can probably create a simple test case to recreate if required. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20725) Camel-Pinecone: Add more producer operations
[ https://issues.apache.org/jira/browse/CAMEL-20725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20725: - Summary: Camel-Pinecone: Add more producer operations (was: Camel-Pinecone: Add more production operations) > Camel-Pinecone: Add more producer operations > > > Key: CAMEL-20725 > URL: https://issues.apache.org/jira/browse/CAMEL-20725 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20726) Camel-Pinecone: Improve Documentation
Andrea Cosentino created CAMEL-20726: Summary: Camel-Pinecone: Improve Documentation Key: CAMEL-20726 URL: https://issues.apache.org/jira/browse/CAMEL-20726 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20725) Camel-Pinecone: Add more production operations
Andrea Cosentino created CAMEL-20725: Summary: Camel-Pinecone: Add more production operations Key: CAMEL-20725 URL: https://issues.apache.org/jira/browse/CAMEL-20725 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842021#comment-17842021
]
Claus Ibsen commented on CAMEL-20724:
-
Can you maybe build an unit test in camel-saxon that reproduces this and send
as PR or attach as file to this JIRA
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
> Fix For: 4.x
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/";);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20724:
Fix Version/s: 4.x
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
> Fix For: 4.x
>
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/";);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20724:
Priority: Minor (was: Major)
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Minor
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/";);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) camel-saxon: xquery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Istomin updated CAMEL-20724:
--
Summary: camel-saxon: xquery fluent API does not work with namespaces
(regression) (was: XQuery fluent API does not work with namespaces
(regression))
> camel-saxon: xquery fluent API does not work with namespaces (regression)
> -
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Major
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/";);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20724) XQuery fluent API does not work with namespaces (regression)
[
https://issues.apache.org/jira/browse/CAMEL-20724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Istomin updated CAMEL-20724:
--
Summary: XQuery fluent API does not work with namespaces (regression)
(was: XQuery fluent API does not work with namespaces (regression from 4.4.0))
> XQuery fluent API does not work with namespaces (regression)
>
>
> Key: CAMEL-20724
> URL: https://issues.apache.org/jira/browse/CAMEL-20724
> Project: Camel
> Issue Type: Bug
> Components: camel-saxon
>Affects Versions: 4.4.0, 4.4.1, 4.4.2, 4.5.0
>Reporter: Denis Istomin
>Priority: Major
>
> This is a regression starting from 4.4.0
> Reproducer:
> [https://github.com/DenisIstomin/camel-xquery-ns-bug]
> Does not work:
> {code:java}
> Namespaces ns = new Namespaces("soap",
> "http://schemas.xmlsoap.org/soap/envelope/";);
> String strExpression = "exists(/soap:Envelope/soap:Header)";
> expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
> {code}
> Throws exception:
> {code:java}
> net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been
> declared
> {code}
> Workaround is to use XQueryBuilder:
> {code:java}
> XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
> xqueryBuilder.setNamespaces(ns.getNamespaces());
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20724) XQuery fluent API does not work with namespaces (regression from 4.4.0)
Denis Istomin created CAMEL-20724:
-
Summary: XQuery fluent API does not work with namespaces
(regression from 4.4.0)
Key: CAMEL-20724
URL: https://issues.apache.org/jira/browse/CAMEL-20724
Project: Camel
Issue Type: Bug
Components: camel-saxon
Affects Versions: 4.5.0, 4.4.2, 4.4.1, 4.4.0
Reporter: Denis Istomin
This is a regression starting from 4.4.0
Reproducer:
[https://github.com/DenisIstomin/camel-xquery-ns-bug]
Does not work:
{code:java}
Namespaces ns = new Namespaces("soap",
"http://schemas.xmlsoap.org/soap/envelope/";);
String strExpression = "exists(/soap:Envelope/soap:Header)";
expression().xquery().expression(strExpression).resultType(String.class).namespaces(ns).end();
{code}
Throws exception:
{code:java}
net.sf.saxon.trans.XPathException: Namespace prefix 'soap' has not been declared
{code}
Workaround is to use XQueryBuilder:
{code:java}
XQueryBuilder xqueryBuilder = xquery(strExpression).resultType(String.class);
xqueryBuilder.setNamespaces(ns.getNamespaces());
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20723) Add a Pinecone Spring Boot Starter component
[ https://issues.apache.org/jira/browse/CAMEL-20723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20723. -- Resolution: Fixed > Add a Pinecone Spring Boot Starter component > > > Key: CAMEL-20723 > URL: https://issues.apache.org/jira/browse/CAMEL-20723 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.6.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20723) Add a Pinecone Spring Boot Starter component
Andrea Cosentino created CAMEL-20723: Summary: Add a Pinecone Spring Boot Starter component Key: CAMEL-20723 URL: https://issues.apache.org/jira/browse/CAMEL-20723 Project: Camel Issue Type: New Feature Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.6.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20702) Add a Pinecone component
[ https://issues.apache.org/jira/browse/CAMEL-20702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20702: - Fix Version/s: 4.6.0 (was: 4.x) > Add a Pinecone component > > > Key: CAMEL-20702 > URL: https://issues.apache.org/jira/browse/CAMEL-20702 > Project: Camel > Issue Type: New Feature >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.6.0 > > > https://www.pinecone.io/ > https://github.com/pinecone-io/pinecone-java-client -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20721. - Resolution: Fixed you can also configure application.properties > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20680) camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration
[ https://issues.apache.org/jira/browse/CAMEL-20680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20680: - Estimated Complexity: Novice (was: Unknown) > camel-kafka: reduce KafkaBreakOnFirstErrorSeekIssueIT test duration > --- > > Key: CAMEL-20680 > URL: https://issues.apache.org/jira/browse/CAMEL-20680 > Project: Camel > Issue Type: Task > Components: camel-kafka >Affects Versions: 4.4.1, 4.5.0 >Reporter: Otavio Rodolfo Piske >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > The test KafkaBreakOnFirstErrorSeekIssueIT takes a very long time to run. > This consumes unnecessary resources from ASF CI. We should investigate how to > improve it to it runs quickly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (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:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20722: - Estimated Complexity: Novice (was: Unknown) > 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 >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > 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] [Updated] (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:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20722: - Description: All the tests named KafkaBreakOnFirst.*IT are unreliable when running on the CI. They fail often, sometimes in multiple archs. (was: The test KafkaBreakOnFirstErrorSeekIssueIT takes a very long time to run. This consumes unnecessary resources from ASF CI. We should investigate how to improve it to it runs quickly.) > 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 >Priority: Major > Labels: help-wanted > Fix For: 4.x > > > 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-20722) camel-kafka: reduce KafkaBreakOnFirstError tests are too unreliable for CIs
Otavio Rodolfo Piske created CAMEL-20722: Summary: 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 Fix For: 4.x The test KafkaBreakOnFirstErrorSeekIssueIT takes a very long time to run. This consumes unnecessary resources from ASF CI. We should investigate how to improve it to it runs quickly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20721: Fix Version/s: 4.6.0 (was: 4.x) > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.6.0 > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20721) camel-jbang - Make it possible to set logging-level per package individually from CLI
[ https://issues.apache.org/jira/browse/CAMEL-20721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20721: --- Assignee: Claus Ibsen > camel-jbang - Make it possible to set logging-level per package individually > from CLI > - > > Key: CAMEL-20721 > URL: https://issues.apache.org/jira/browse/CAMEL-20721 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.x > > > So you can do something like > camel run * --logging-level=com.foo=WARN --logging-level=com.bar=DEBUG > Or come up with a new name of the CLI as logging-level is for global I think -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20651) camel-jbang - The open-api should use the new contract-first openapi
[ https://issues.apache.org/jira/browse/CAMEL-20651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20651. - Resolution: Fixed > camel-jbang - The open-api should use the new contract-first openapi > - > > Key: CAMEL-20651 > URL: https://issues.apache.org/jira/browse/CAMEL-20651 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.6.0 > > > Instead of code generating rest-dsl we can just use the new openapi > contract-first instead: CAMEL-20557 -- This message was sent by Atlassian Jira (v8.20.10#820010)
