[jira] [Resolved] (CAMEL-14629) Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same worked with Karaf 4.2.7 w/ Camel 3.0.1)
[
https://issues.apache.org/jira/browse/CAMEL-14629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved CAMEL-14629.
-
Fix Version/s: (was: 3.1.1)
Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré)
Resolution: Fixed
> Install of camel-jackson on Karaf 4.2.7 w/ Camel 3.1.0 causes an error (same
> worked with Karaf 4.2.7 w/ Camel 3.0.1)
>
>
> Key: CAMEL-14629
> URL: https://issues.apache.org/jira/browse/CAMEL-14629
> Project: Camel
> Issue Type: Bug
> Components: camel-jackson
>Affects Versions: 3.1.0
>Reporter: Gerald Kallas
>Assignee: Guillaume Nodet
>Priority: Major
> Fix For: 3.2.0
>
>
> I tried to upgrade from Karaf 4.2.7 w/ Camel 3.0.1 towards Karaf 4.2.7 w/
> Camel 3.1.0. Same behaviour also with Karaf 4.2.8 w/ Camel 3.1.0
>
> While executing these commands
>
>
> {code:java}
> karaf@root()> feature:repo-add hawtio 2.9.1
> Adding feature url mvn:io.hawt/hawtio-karaf/2.9.1/xml/features
> karaf@root()> feature:repo-add activemq 5.15.11
> Adding feature url mvn:org.apache.activemq/activemq-karaf/5.15.11/xml/features
> karaf@root()> feature:repo-add camel 3.1.0
> Adding feature url mvn:org.apache.camel.karaf/apache-camel/3.1.0/xml/features
> karaf@root()> feature:install webconsole hawtio activemq-broker-noweb camel
> camel-jms jms camel-http camel-jetty camel-swagger-java camel-ftp
> camel-jackson camel-jsonpath camel-zipfile camel-velocity camel-groovy {code}
>
> I'm getting the following error
>
>
> {code:java}
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
> missing requirement [root] osgi.identity; osgi.identity=camel-jackson;
> type=karaf.feature; version="[3.1.0,3.1.0]";
> filter:="(&(osgi.identity=camel-jackson)(type=karaf.feature)(version>=3.1.0)(version<=3.1.0))"
> [caused by: Unable to resolve camel-jackson/3.1.0: missing requirement
> [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package; filter:="(&(osgi.wiring.package=
> javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]] at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> at org.apache.felix.resolver.ResolverImpl.doResolve(ResolverImpl.java:392)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:378) at
> org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:332) at
> org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:257)
> at
> org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:393)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062)
> at
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Caused by:
> org.apache.felix.resolver.reason.ReasonException: Unable to resolve
> camel-jackson/3.1.0: missing requirement [camel-jackson/3.1.0] osgi.identity;
> osgi.identity=org.apache.camel.camel-jackson; type=osgi.bundle;
> version="[3.1.0,3.1.0]"; resolution:=mandatory [caused by: Unable to resolve
> org.apache.camel.camel-jackson/3.1.0: missing requirement
> [org.apache.camel.camel-jackson/3.1.0] osgi.wiring.package;
> filter:="(&(osgi.wiring.package=com.fasterxml.jackson.module.jaxb)(version>=2.9.0)(!(version>=3.0.0)))"
> [caused by: Unable to resolve
> com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2: missing
> requirement
> [com.fasterxml.jackson.module.jackson-module-jaxb-annotations/2.10.2]
> osgi.wiring.package;
> filter:="(&(osgi.wiring.package=javax.xml.bind)(version>=2.3.0)(!(version>=3.0.0)))"]]
> at
> org.apache.felix.resolver.Candidates$MissingRequirementError.toException(Candidates.java:1343)
> ... 12 more Caused by: org.apache.felix.resolver.reason.ReasonException:
[jira] [Commented] (CAMEL-14567) camel-website - Sidebar menu tidy up names
[ https://issues.apache.org/jira/browse/CAMEL-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068989#comment-17068989 ] Rimsha Chaudhry commented on CAMEL-14567: - [~zregvart] hi I made changes in the antora.yml of required documentations , however to test run the changes do I require to run the documentation module? However that still would not preview me how the changes are appearing in the main website,could you guide me here ? > camel-website - Sidebar menu tidy up names > -- > > Key: CAMEL-14567 > URL: https://issues.apache.org/jira/browse/CAMEL-14567 > Project: Camel > Issue Type: Test >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, website > Attachments: Screenshot_2020-03-23 Apache Camel user manual - Apache > Camel.png > > > Apache Camel extensions for Quarkus > Apache Camel K > Apache Camel Kafka Connector > Camel Spring Boot Starters > Component reference > User manual > Make this into > Camel Components > Camel Kafka Connectors > Camel Quarkus Extensions > Camel Spring Boot Starters > User manual -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068963#comment-17068963 ] Andrea Cosentino commented on CAMEL-14770: -- This is already fixed and resolved > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > Attachments: camel_build_error.JPG > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-14770: Assignee: David Jencks > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > Attachments: camel_build_error.JPG > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14770. -- Resolution: Fixed > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > Attachments: camel_build_error.JPG > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solange Iyubu updated CAMEL-14770: -- Attachment: camel_build_error.JPG > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Priority: Major > Fix For: 3.2.0 > > Attachments: camel_build_error.JPG > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068923#comment-17068923 ] Solange Iyubu commented on CAMEL-14770: --- Whenever I try to build the camel website using mvnw.cmd clean install or mvn clean install -Pfastinstall I am getting the error of maven failing to execute maven-surefire-plugin:3.0.0-M4. any help? > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Priority: Major > Fix For: 3.2.0 > > Attachments: camel_build_error.JPG > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14804) camel-servlet-osgi - Move osgi bits to camel-karaf
[ https://issues.apache.org/jira/browse/CAMEL-14804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14804. - Resolution: Fixed > camel-servlet-osgi - Move osgi bits to camel-karaf > -- > > Key: CAMEL-14804 > URL: https://issues.apache.org/jira/browse/CAMEL-14804 > Project: Camel > Issue Type: Task > Components: camel-servlet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > We can move the OSGi bits out of camel-servlet into a new camel-servlet-osgi > component in camel-karaf so it has control of OSGi there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068805#comment-17068805 ] David Jencks commented on CAMEL-14770: -- I think I fixed this with the associated PR and just forgot to resolve the issue. Is there anything left to do? > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14804) camel-servlet-osgi - Move osgi bits to camel-karaf
[ https://issues.apache.org/jira/browse/CAMEL-14804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-14804: --- Assignee: Claus Ibsen > camel-servlet-osgi - Move osgi bits to camel-karaf > -- > > Key: CAMEL-14804 > URL: https://issues.apache.org/jira/browse/CAMEL-14804 > Project: Camel > Issue Type: Task > Components: camel-servlet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > We can move the OSGi bits out of camel-servlet into a new camel-servlet-osgi > component in camel-karaf so it has control of OSGi there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14804) camel-servlet-osgi - Move osgi bits to camel-karaf
[ https://issues.apache.org/jira/browse/CAMEL-14804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068783#comment-17068783 ] Claus Ibsen commented on CAMEL-14804: - There are a few other components that has osgi starters that we can move to camel-karaf so they are maintained over there > camel-servlet-osgi - Move osgi bits to camel-karaf > -- > > Key: CAMEL-14804 > URL: https://issues.apache.org/jira/browse/CAMEL-14804 > Project: Camel > Issue Type: Task > Components: camel-servlet >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.2.0 > > > We can move the OSGi bits out of camel-servlet into a new camel-servlet-osgi > component in camel-karaf so it has control of OSGi there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14781) Support page missing toolbar breadcrumbs
[ https://issues.apache.org/jira/browse/CAMEL-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solange Iyubu updated CAMEL-14781: -- Attachment: no toolbar nor nav_LI.jpg > Support page missing toolbar breadcrumbs > > > Key: CAMEL-14781 > URL: https://issues.apache.org/jira/browse/CAMEL-14781 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: no toolbar nor nav_LI.jpg, no toolbar nor nav_LI.jpg > > > While navigating on apache website I saw pages that don't have toolbars > breadcrumps such as support page from community. I am going to work on it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14677) Incorporate the swoosh design element in the rest of the website
[ https://issues.apache.org/jira/browse/CAMEL-14677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068634#comment-17068634 ] Luana Faustini commented on CAMEL-14677: [~raashika03] go ahead! I won't be able to work on this. Good luck! [~zregvart] thanks for the care. > Incorporate the swoosh design element in the rest of the website > > > Key: CAMEL-14677 > URL: https://issues.apache.org/jira/browse/CAMEL-14677 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > We feature a swoosh on the front page of the website (the wavy lines > currently behind the "Camel 3.1 is here! what's new" text). > It would be interesting to see it incorporated in the rest of the website. > For example I think it would be nice to add it as a separator beneath the > main topmost navigation. And in that case perhaps not as a wavy line, but as > few narrow straight lines. > An interesting transition animation can be then done from the large swoosh > that's present now and fixed in place, to this separating lines just below > the topmost navigation. > Also see CAMEL-14676 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068598#comment-17068598 ] Solange Iyubu commented on CAMEL-14770: --- I am working on this issue > Sort nav the same as index pages > > > Key: CAMEL-14770 > URL: https://issues.apache.org/jira/browse/CAMEL-14770 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The nav files are sorted by file name whereas the index page tables are > sorted by doc title (case insensitive). I already fixed this for the 2.x and > 3.0.x components website versions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14804) camel-servlet-osgi - Move osgi bits to camel-karaf
Claus Ibsen created CAMEL-14804: --- Summary: camel-servlet-osgi - Move osgi bits to camel-karaf Key: CAMEL-14804 URL: https://issues.apache.org/jira/browse/CAMEL-14804 Project: Camel Issue Type: Task Components: camel-servlet Reporter: Claus Ibsen Fix For: 3.2.0 We can move the OSGi bits out of camel-servlet into a new camel-servlet-osgi component in camel-karaf so it has control of OSGi there. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14798) Separate Avro dataformat out of camel-avro component
[ https://issues.apache.org/jira/browse/CAMEL-14798?focusedWorklogId=411014=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-411014 ] ASF GitHub Bot logged work on CAMEL-14798: -- Author: ASF GitHub Bot Created on: 27/Mar/20 11:33 Start Date: 27/Mar/20 11:33 Worklog Time Spent: 10m Work Description: mmelko commented on pull request #3686: CAMEL-14798: Separate Avro RPC functionality out of camel-avro URL: https://github.com/apache/camel/pull/3686 With this PR `camel-avro` component implements only Avro dataformat for camel. All rpc functionality was separated into new component `camel-avro-rpc`. Documentation of components was changed accordingly. [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful subject line and body. [ ] If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. [ ] Run `mvn clean install -Psourcecheck` in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically. Below are the contribution guidelines: https://github.com/apache/camel/blob/master/CONTRIBUTING.md This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 411014) Remaining Estimate: 0h Time Spent: 10m > Separate Avro dataformat out of camel-avro component > > > Key: CAMEL-14798 > URL: https://issues.apache.org/jira/browse/CAMEL-14798 > Project: Camel > Issue Type: Improvement > Components: camel-avro >Reporter: Matej Melko >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently camel-avro consist of two parts, avro dataformat and camel-avro > component used for RPC. Separation could help to support avro at least > partially as a native camel-quarkus extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14640) CVEs in the library dependencies
[ https://issues.apache.org/jira/browse/CAMEL-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14640. - Fix Version/s: 3.2.0 Resolution: Fixed Only camel-jcr cannot upgrade to a newer Lucene version at this moment. Its tracked by Apache Jackrabbit project as its a problem in their library. The Camel side has been fixed > CVEs in the library dependencies > > > Key: CAMEL-14640 > URL: https://issues.apache.org/jira/browse/CAMEL-14640 > Project: Camel > Issue Type: Task >Reporter: XuCongying >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.2.0 > > Attachments: apache-camel_CVE-report.md > > > Hi, I found that your project are using some vulnerable dependencies. To > prevent potential risk it may cause, I suggest a library update. Here is the > details: > Vulnerable Library Version: com.squareup.okhttp3 : okhttp : 3.11.0 > CVE ID: > [CVE-2018-20200](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20200) > Import Path: components/camel-jetty/pom.xml > Suggested Safe Versions: 3.12.1, 3.12.2, 3.12.3, 3.12.4, 3.12.5, 3.12.6, > 3.12.7, 3.12.8, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.14.2, 3.14.3, 3.14.4, > 3.14.5, 3.14.6, 4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3, 4.0.0-alpha01, > 4.0.0-alpha02, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0 > Vulnerable Library Version: org.apache.tomcat.embed : tomcat-embed-core : > 8.5.0 > CVE ID: > [CVE-2016-0762](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762), > > [CVE-2017-5650](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650), > > [CVE-2016-6797](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797), > > [CVE-2017-5647](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647), > > [CVE-2017-5664](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664), > > [CVE-2017-12617](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617), > > [CVE-2016-3092](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092), > > [CVE-2019-0199](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0199), > > [CVE-2017-5648](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648), > > [CVE-2019-10072](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10072), > [CVE-2017-5651](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651) > Import Path: components/camel-servlet/pom.xml > Suggested Safe Versions: 10.0.0-M1, 8.5.41, 8.5.42, 8.5.43, 8.5.45, 8.5.46, > 8.5.47, 8.5.49, 8.5.50, 8.5.51, 9.0.27, 9.0.29, 9.0.30, 9.0.31 > Vulnerable Library Version: org.apache.spark : spark-core_2.11 : 2.4.4 > CVE ID: > [CVE-2017-7678](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7678) > Import Path: components/camel-spark/pom.xml > Suggested Safe Versions: 2.4.5 > Vulnerable Library Version: org.apache.lucene : lucene-core : 3.6.0 > CVE ID: > [CVE-2017-3163](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3163) > Import Path: components/camel-jcr/pom.xml > Suggested Safe Versions: 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, > 6.6.3, 6.6.4, 6.6.5, 6.6.6, 7.0.0, 7.0.1, 7.1.0, 7.2.0, 7.2.1, 7.3.0, 7.3.1, > 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.1, 7.7.2, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, > 8.3.1, 8.4.0, 8.4.1 > Vulnerable Library Version: org.apache.logging.log4j : log4j-api : 2.7 > CVE ID: > [CVE-2017-5645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645) > Import Path: examples/camel-example-google-pubsub/pom.xml, > examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml > Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, > 2.13.0, 2.8.2, 2.9.0, 2.9.1 > Vulnerable Library Version: org.apache.hadoop : hadoop-hdfs : 2.7.4 > CVE ID: > [CVE-2018-11768](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11768) > Import Path: components/camel-hdfs/pom.xml, components/camel-hbase/pom.xml, > components/camel-hbase/pom.xml > Suggested Safe Versions: 2.10.0, 2.8.5, 2.9.2, 3.1.2, 3.1.3, 3.2.0, 3.2.1 > Vulnerable Library Version: org.apache.logging.log4j : log4j-core : 2.7 > CVE ID: > [CVE-2019-17571](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571), > [CVE-2017-5645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645) > Import Path: examples/camel-example-google-pubsub/pom.xml, > examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml > Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, > 2.13.0, 2.8.2, 2.9.0, 2.9.1 > Vulnerable Library Version: org.asynchttpclient : async-http-client : 2.0.16 > CVE ID: > [CVE-2017-14063](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14063) > Import Path: components/camel-websocket/pom.xml >
[jira] [Comment Edited] (CAMEL-14640) CVEs in the library dependencies
[ https://issues.apache.org/jira/browse/CAMEL-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049370#comment-17049370 ] Claus Ibsen edited comment on CAMEL-14640 at 3/27/20, 10:52 AM: Status will be reported here -Vulnerable Library Version: com.squareup.okhttp3 : okhttp : 3.11.0- CVE ID: [CVE-2018-20200]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20200]) Import Path: components/camel-jetty/pom.xml Suggested Safe Versions: 3.12.1, 3.12.2, 3.12.3, 3.12.4, 3.12.5, 3.12.6, 3.12.7, 3.12.8, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.14.2, 3.14.3, 3.14.4, 3.14.5, 3.14.6, 4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3, 4.0.0-alpha01, 4.0.0-alpha02, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0 -Vulnerable Library Version: org.apache.tomcat.embed : tomcat-embed-core : 8.5.0- CVE ID: [CVE-2016-0762]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]), [CVE-2017-5650]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650]), [CVE-2016-6797]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]), [CVE-2017-5647]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647]), [CVE-2017-5664]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664]), [CVE-2017-12617]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]), [CVE-2016-3092]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]), [CVE-2019-0199]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0199]), [CVE-2017-5648]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648]), [CVE-2019-10072]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10072]), [CVE-2017-5651]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651]) Import Path: components/camel-servlet/pom.xml Suggested Safe Versions: 10.0.0-M1, 8.5.41, 8.5.42, 8.5.43, 8.5.45, 8.5.46, 8.5.47, 8.5.49, 8.5.50, 8.5.51, 9.0.27, 9.0.29, 9.0.30, 9.0.31 -Vulnerable Library Version: org.apache.spark : spark-core_2.11 : 2.4.4- CVE ID: [CVE-2017-7678]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7678]) Import Path: components/camel-spark/pom.xml Suggested Safe Versions: 2.4.5 Vulnerable Library Version: org.apache.lucene : lucene-core : 3.6.0 CVE ID: [CVE-2017-3163]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3163]) Import Path: components/camel-jcr/pom.xml Suggested Safe Versions: 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 7.0.0, 7.0.1, 7.1.0, 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.1, 7.7.2, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, 8.3.1, 8.4.0, 8.4.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-api : 2.7- CVE ID: [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.apache.hadoop : hadoop-hdfs : 2.7.4- CVE ID: [CVE-2018-11768]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11768]) Import Path: components/camel-hdfs/pom.xml, components/camel-hbase/pom.xml, components/camel-hbase/pom.xml Suggested Safe Versions: 2.10.0, 2.8.5, 2.9.2, 3.1.2, 3.1.3, 3.2.0, 3.2.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-core : 2.7- CVE ID: [CVE-2019-17571]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571]), [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.asynchttpclient : async-http-client : 2.0.16- CVE ID: [CVE-2017-14063]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14063]) Import Path: components/camel-websocket/pom.xml Suggested Safe Versions: 2.0.35, 2.0.36, 2.0.37, 2.0.38, 2.0.39, 2.0.40, 2.1.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-alpha1, 2.1.0-alpha10, 2.1.0-alpha11, 2.1.0-alpha12, 2.1.0-alpha13, 2.1.0-alpha14, 2.1.0-alpha15, 2.1.0-alpha16, 2.1.0-alpha17, 2.1.0-alpha18, 2.1.0-alpha19, 2.1.0-alpha2, 2.1.0-alpha20, 2.1.0-alpha21, 2.1.0-alpha22, 2.1.0-alpha23, 2.1.0-alpha24, 2.1.0-alpha25, 2.1.0-alpha26, 2.1.0-alpha3, 2.1.0-alpha4, 2.1.0-alpha5, 2.1.0-alpha6, 2.1.0-alpha7, 2.1.0-alpha8, 2.1.0-alpha9, 2.1.1, 2.1.2, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.9.0 -Vulnerable Library Version: commons-httpclient : commons-httpclient : 3.1- CVE
[jira] [Updated] (CAMEL-14781) Support page missing toolbar breadcrumbs
[ https://issues.apache.org/jira/browse/CAMEL-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solange Iyubu updated CAMEL-14781: -- Attachment: no toolbar nor nav_LI.jpg How about navigation bar at right side of the page, also some pages don't have it *Solange Iyubu* Student Carnegie Mellon University in Africa Tel: +250 785 562 715 On Fri, Mar 27, 2020 at 12:29 PM Zoran Regvart (Jira) > Support page missing toolbar breadcrumbs > > > Key: CAMEL-14781 > URL: https://issues.apache.org/jira/browse/CAMEL-14781 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: no toolbar nor nav_LI.jpg > > > While navigating on apache website I saw pages that don't have toolbars > breadcrumps such as support page from community. I am going to work on it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14640) CVEs in the library dependencies
[ https://issues.apache.org/jira/browse/CAMEL-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049370#comment-17049370 ] Claus Ibsen edited comment on CAMEL-14640 at 3/27/20, 10:45 AM: Status will be reported here -Vulnerable Library Version: com.squareup.okhttp3 : okhttp : 3.11.0- CVE ID: [CVE-2018-20200]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20200]) Import Path: components/camel-jetty/pom.xml Suggested Safe Versions: 3.12.1, 3.12.2, 3.12.3, 3.12.4, 3.12.5, 3.12.6, 3.12.7, 3.12.8, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.14.2, 3.14.3, 3.14.4, 3.14.5, 3.14.6, 4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3, 4.0.0-alpha01, 4.0.0-alpha02, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0 -Vulnerable Library Version: org.apache.tomcat.embed : tomcat-embed-core : 8.5.0- CVE ID: [CVE-2016-0762]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]), [CVE-2017-5650]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650]), [CVE-2016-6797]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]), [CVE-2017-5647]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647]), [CVE-2017-5664]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664]), [CVE-2017-12617]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]), [CVE-2016-3092]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]), [CVE-2019-0199]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0199]), [CVE-2017-5648]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648]), [CVE-2019-10072]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10072]), [CVE-2017-5651]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651]) Import Path: components/camel-servlet/pom.xml Suggested Safe Versions: 10.0.0-M1, 8.5.41, 8.5.42, 8.5.43, 8.5.45, 8.5.46, 8.5.47, 8.5.49, 8.5.50, 8.5.51, 9.0.27, 9.0.29, 9.0.30, 9.0.31 -Vulnerable Library Version: org.apache.spark : spark-core_2.11 : 2.4.4- CVE ID: [CVE-2017-7678]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7678]) Import Path: components/camel-spark/pom.xml Suggested Safe Versions: 2.4.5 Vulnerable Library Version: org.apache.lucene : lucene-core : 3.6.0 CVE ID: [CVE-2017-3163]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3163]) Import Path: components/camel-jcr/pom.xml Suggested Safe Versions: 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 7.0.0, 7.0.1, 7.1.0, 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.1, 7.7.2, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, 8.3.1, 8.4.0, 8.4.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-api : 2.7- CVE ID: [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.apache.hadoop : hadoop-hdfs : 2.7.4- CVE ID: [CVE-2018-11768]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11768]) Import Path: components/camel-hdfs/pom.xml, components/camel-hbase/pom.xml, components/camel-hbase/pom.xml Suggested Safe Versions: 2.10.0, 2.8.5, 2.9.2, 3.1.2, 3.1.3, 3.2.0, 3.2.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-core : 2.7- CVE ID: [CVE-2019-17571]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571]), [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.asynchttpclient : async-http-client : 2.0.16- CVE ID: [CVE-2017-14063]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14063]) Import Path: components/camel-websocket/pom.xml Suggested Safe Versions: 2.0.35, 2.0.36, 2.0.37, 2.0.38, 2.0.39, 2.0.40, 2.1.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-alpha1, 2.1.0-alpha10, 2.1.0-alpha11, 2.1.0-alpha12, 2.1.0-alpha13, 2.1.0-alpha14, 2.1.0-alpha15, 2.1.0-alpha16, 2.1.0-alpha17, 2.1.0-alpha18, 2.1.0-alpha19, 2.1.0-alpha2, 2.1.0-alpha20, 2.1.0-alpha21, 2.1.0-alpha22, 2.1.0-alpha23, 2.1.0-alpha24, 2.1.0-alpha25, 2.1.0-alpha26, 2.1.0-alpha3, 2.1.0-alpha4, 2.1.0-alpha5, 2.1.0-alpha6, 2.1.0-alpha7, 2.1.0-alpha8, 2.1.0-alpha9, 2.1.1, 2.1.2, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.9.0 -Vulnerable Library Version: commons-httpclient : commons-httpclient : 3.1- CVE
[jira] [Comment Edited] (CAMEL-14640) CVEs in the library dependencies
[ https://issues.apache.org/jira/browse/CAMEL-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049370#comment-17049370 ] Claus Ibsen edited comment on CAMEL-14640 at 3/27/20, 10:44 AM: Status will be reported here -Vulnerable Library Version: com.squareup.okhttp3 : okhttp : 3.11.0- CVE ID: [CVE-2018-20200]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20200]) Import Path: components/camel-jetty/pom.xml Suggested Safe Versions: 3.12.1, 3.12.2, 3.12.3, 3.12.4, 3.12.5, 3.12.6, 3.12.7, 3.12.8, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.14.2, 3.14.3, 3.14.4, 3.14.5, 3.14.6, 4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3, 4.0.0-alpha01, 4.0.0-alpha02, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0 -Vulnerable Library Version: org.apache.tomcat.embed : tomcat-embed-core : 8.5.0- CVE ID: [CVE-2016-0762]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]), [CVE-2017-5650]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650]), [CVE-2016-6797]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]), [CVE-2017-5647]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647]), [CVE-2017-5664]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664]), [CVE-2017-12617]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]), [CVE-2016-3092]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]), [CVE-2019-0199]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0199]), [CVE-2017-5648]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648]), [CVE-2019-10072]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10072]), [CVE-2017-5651]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651]) Import Path: components/camel-servlet/pom.xml Suggested Safe Versions: 10.0.0-M1, 8.5.41, 8.5.42, 8.5.43, 8.5.45, 8.5.46, 8.5.47, 8.5.49, 8.5.50, 8.5.51, 9.0.27, 9.0.29, 9.0.30, 9.0.31 -Vulnerable Library Version: org.apache.spark : spark-core_2.11 : 2.4.4- CVE ID: [CVE-2017-7678]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7678]) Import Path: components/camel-spark/pom.xml Suggested Safe Versions: 2.4.5 Vulnerable Library Version: org.apache.lucene : lucene-core : 3.6.0 CVE ID: [CVE-2017-3163]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3163]) Import Path: components/camel-jcr/pom.xml Suggested Safe Versions: 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 7.0.0, 7.0.1, 7.1.0, 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.1, 7.7.2, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, 8.3.1, 8.4.0, 8.4.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-api : 2.7- CVE ID: [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 Vulnerable Library Version: org.apache.hadoop : hadoop-hdfs : 2.7.4 CVE ID: [CVE-2018-11768]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11768]) Import Path: components/camel-hdfs/pom.xml, components/camel-hbase/pom.xml, components/camel-hbase/pom.xml Suggested Safe Versions: 2.10.0, 2.8.5, 2.9.2, 3.1.2, 3.1.3, 3.2.0, 3.2.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-core : 2.7- CVE ID: [CVE-2019-17571]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571]), [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.asynchttpclient : async-http-client : 2.0.16- CVE ID: [CVE-2017-14063]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14063]) Import Path: components/camel-websocket/pom.xml Suggested Safe Versions: 2.0.35, 2.0.36, 2.0.37, 2.0.38, 2.0.39, 2.0.40, 2.1.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-alpha1, 2.1.0-alpha10, 2.1.0-alpha11, 2.1.0-alpha12, 2.1.0-alpha13, 2.1.0-alpha14, 2.1.0-alpha15, 2.1.0-alpha16, 2.1.0-alpha17, 2.1.0-alpha18, 2.1.0-alpha19, 2.1.0-alpha2, 2.1.0-alpha20, 2.1.0-alpha21, 2.1.0-alpha22, 2.1.0-alpha23, 2.1.0-alpha24, 2.1.0-alpha25, 2.1.0-alpha26, 2.1.0-alpha3, 2.1.0-alpha4, 2.1.0-alpha5, 2.1.0-alpha6, 2.1.0-alpha7, 2.1.0-alpha8, 2.1.0-alpha9, 2.1.1, 2.1.2, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.9.0 -Vulnerable Library Version: commons-httpclient : commons-httpclient : 3.1- CVE
[jira] [Comment Edited] (CAMEL-14640) CVEs in the library dependencies
[ https://issues.apache.org/jira/browse/CAMEL-14640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17049370#comment-17049370 ] Claus Ibsen edited comment on CAMEL-14640 at 3/27/20, 10:33 AM: Status will be reported here -Vulnerable Library Version: com.squareup.okhttp3 : okhttp : 3.11.0- CVE ID: [CVE-2018-20200]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20200]) Import Path: components/camel-jetty/pom.xml Suggested Safe Versions: 3.12.1, 3.12.2, 3.12.3, 3.12.4, 3.12.5, 3.12.6, 3.12.7, 3.12.8, 3.13.0, 3.13.1, 3.14.0, 3.14.1, 3.14.2, 3.14.3, 3.14.4, 3.14.5, 3.14.6, 4.0.0, 4.0.0-RC1, 4.0.0-RC2, 4.0.0-RC3, 4.0.0-alpha01, 4.0.0-alpha02, 4.0.1, 4.1.0, 4.1.1, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.4.0 -Vulnerable Library Version: org.apache.tomcat.embed : tomcat-embed-core : 8.5.0- CVE ID: [CVE-2016-0762]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0762]), [CVE-2017-5650]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5650]), [CVE-2016-6797]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6797]), [CVE-2017-5647]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5647]), [CVE-2017-5664]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5664]), [CVE-2017-12617]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12617]), [CVE-2016-3092]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]), [CVE-2019-0199]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0199]), [CVE-2017-5648]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5648]), [CVE-2019-10072]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10072]), [CVE-2017-5651]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5651]) Import Path: components/camel-servlet/pom.xml Suggested Safe Versions: 10.0.0-M1, 8.5.41, 8.5.42, 8.5.43, 8.5.45, 8.5.46, 8.5.47, 8.5.49, 8.5.50, 8.5.51, 9.0.27, 9.0.29, 9.0.30, 9.0.31 -Vulnerable Library Version: org.apache.spark : spark-core_2.11 : 2.4.4- CVE ID: [CVE-2017-7678]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7678]) Import Path: components/camel-spark/pom.xml Suggested Safe Versions: 2.4.5 Vulnerable Library Version: org.apache.lucene : lucene-core : 3.6.0 CVE ID: [CVE-2017-3163]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3163]) Import Path: components/camel-jcr/pom.xml Suggested Safe Versions: 6.4.1, 6.4.2, 6.5.0, 6.5.1, 6.6.0, 6.6.1, 6.6.2, 6.6.3, 6.6.4, 6.6.5, 6.6.6, 7.0.0, 7.0.1, 7.1.0, 7.2.0, 7.2.1, 7.3.0, 7.3.1, 7.4.0, 7.5.0, 7.6.0, 7.7.0, 7.7.1, 7.7.2, 8.0.0, 8.1.0, 8.1.1, 8.2.0, 8.3.0, 8.3.1, 8.4.0, 8.4.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-api : 2.7- CVE ID: [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 Vulnerable Library Version: org.apache.hadoop : hadoop-hdfs : 2.7.4 CVE ID: [CVE-2018-11768]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11768]) Import Path: components/camel-hdfs/pom.xml, components/camel-hbase/pom.xml, components/camel-hbase/pom.xml Suggested Safe Versions: 2.10.0, 2.8.5, 2.9.2, 3.1.2, 3.1.3, 3.2.0, 3.2.1 -Vulnerable Library Version: org.apache.logging.log4j : log4j-core : 2.7- CVE ID: [CVE-2019-17571]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571]), [CVE-2017-5645]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5645]) Import Path: examples/camel-example-google-pubsub/pom.xml, examples/camel-example-kafka/pom.xml, examples/camel-example-debezium/pom.xml Suggested Safe Versions: 2.10.0, 2.11.0, 2.11.1, 2.11.2, 2.12.0, 2.12.1, 2.13.0, 2.8.2, 2.9.0, 2.9.1 -Vulnerable Library Version: org.asynchttpclient : async-http-client : 2.0.16- CVE ID: [CVE-2017-14063]([https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14063]) Import Path: components/camel-websocket/pom.xml Suggested Safe Versions: 2.0.35, 2.0.36, 2.0.37, 2.0.38, 2.0.39, 2.0.40, 2.1.0, 2.1.0-RC1, 2.1.0-RC2, 2.1.0-RC3, 2.1.0-RC4, 2.1.0-alpha1, 2.1.0-alpha10, 2.1.0-alpha11, 2.1.0-alpha12, 2.1.0-alpha13, 2.1.0-alpha14, 2.1.0-alpha15, 2.1.0-alpha16, 2.1.0-alpha17, 2.1.0-alpha18, 2.1.0-alpha19, 2.1.0-alpha2, 2.1.0-alpha20, 2.1.0-alpha21, 2.1.0-alpha22, 2.1.0-alpha23, 2.1.0-alpha24, 2.1.0-alpha25, 2.1.0-alpha26, 2.1.0-alpha3, 2.1.0-alpha4, 2.1.0-alpha5, 2.1.0-alpha6, 2.1.0-alpha7, 2.1.0-alpha8, 2.1.0-alpha9, 2.1.1, 2.1.2, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.10.4, 2.10.5, 2.2.0, 2.2.1, 2.3.0, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.6.0, 2.7.0, 2.8.0, 2.8.1, 2.9.0 -Vulnerable Library Version: commons-httpclient : commons-httpclient : 3.1- CVE
[jira] [Commented] (CAMEL-14781) Support page missing toolbar breadcrumbs
[ https://issues.apache.org/jira/browse/CAMEL-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068531#comment-17068531 ] Zoran Regvart commented on CAMEL-14781: --- There are two generators generating the HTML content published for the website [Hugo|https://gohugo.io/] and [Antora|https://antora.org/], we have this documented in the website [README.md|https://github.com/apache/camel-website/blob/master/README.md]. Only Antora built content (the documentation) has breadcrumbs. I'm not sure we need breadcrumbs but I'll entertain the notion that we might. For that the changes need to go to Hugo layouts. We would need a partial that we could add to some of the layouts (we don't need breadcrumbs on the front page for example). > Support page missing toolbar breadcrumbs > > > Key: CAMEL-14781 > URL: https://issues.apache.org/jira/browse/CAMEL-14781 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Solange Iyubu >Priority: Major > > While navigating on apache website I saw pages that don't have toolbars > breadcrumps such as support page from community. I am going to work on it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14797) Quick Look Up- The search results do not appear properly
[ https://issues.apache.org/jira/browse/CAMEL-14797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068522#comment-17068522 ] Zoran Regvart commented on CAMEL-14797: --- Yeah when did not have modules within the "components" Antora component and now we do, so there's extra markup that the [quick search JavaScript|https://github.com/apache/camel-website/blob/master/antora-ui-camel/src/js/05-nav-search.js] doesn't toggle. > Quick Look Up- The search results do not appear properly > > > Key: CAMEL-14797 > URL: https://issues.apache.org/jira/browse/CAMEL-14797 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Prerna Singh >Priority: Major > Attachments: image-2020-03-26-15-00-38-202.png > > > The search results of 'Quick Look up' in documentation section does not yield > search results properly. > Here an extra arrow appears and also when we click that, it looks messed up. > When we click the arrow near the search result which appeared, the whole > search result disappears and then does not even appear if we write it again > in the Quick Look up search bar. > !image-2020-03-26-15-00-38-202.png|width=1130,height=636! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14175) Getting Started guide should be more informative and concise
[ https://issues.apache.org/jira/browse/CAMEL-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068511#comment-17068511 ] Zoran Regvart commented on CAMEL-14175: --- Hi [~Gracie] please see above comment by [~praveenkottarat...@gmail.com] and the work already done. Please don't duplicate any work. > Getting Started guide should be more informative and concise > - > > Key: CAMEL-14175 > URL: https://issues.apache.org/jira/browse/CAMEL-14175 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Omar Al-Safi >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > The [current > guide|https://camel.apache.org/manual/latest/getting-started.html] may > lacking some info the may help users to get started with Camel. It would make > sense to re-write this guide -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13181) camel-salesforce - rest exception parsing produces useless messages
[
https://issues.apache.org/jira/browse/CAMEL-13181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068504#comment-17068504
]
Zoran Regvart commented on CAMEL-13181:
---
[~Soann Dewasme] I think that's a good idea. I think what we can improve here
is twofold: have a meaningful error text displayed instead of the
{{InputStream::toString}} and have a parameter to display the full/raw errors
from Salesforce. First might require parsing the error responses from
Salesforce, for the second improvement perhaps a {{rawErrors}} (we already have
{{rawPayload}} can that be used for errors also?) would be a good property
name. Not sure if we should consider capping the number of characters/bytes in
error output or redacting some of the output so we don't output passwords or
similar sensitive data.
> camel-salesforce - rest exception parsing produces useless messages
> ---
>
> Key: CAMEL-13181
> URL: https://issues.apache.org/jira/browse/CAMEL-13181
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
>Reporter: Jesse Sightler
>Priority: Minor
>
> In the case of serialization failures, createRestException swallows the
> exception and logs the inputstream object itself:
>
> [https://github.com/apache/camel/blob/master/components/camel-salesforce/camel-salesforce-component/src/main/java/org/apache/camel/component/salesforce/internal/client/DefaultRestClient.java#L119]
>
> This does not tend to produce an error message, as the response is
> essentially always something like "ByteArrayInputStream@\{hashcode}". Perhaps
> it could try to return the raw contents if it is short and json?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14677) Incorporate the swoosh design element in the rest of the website
[ https://issues.apache.org/jira/browse/CAMEL-14677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068498#comment-17068498 ] Zoran Regvart commented on CAMEL-14677: --- [~raashika03] feel free to work on this, not sure if [~Devkant Gorai] or [~luanafaustini] are working on this, I haven't seen any pull requests or comments on that here. You're free to reach out to them directly and see if they're still working on this. The goal is to include the design of the swoosh thought the website, not in the same way it's shown on the front page. I've provided one example of an idea: to incorporate it as a divider between the top navigation and the rest of the webpage and have it animate from the large swoosh into the divider. But what we have here is just an idea, I would be interested in seeing mockups or other ideas on how to incorporate the swoosh design element in the rest of the website. > Incorporate the swoosh design element in the rest of the website > > > Key: CAMEL-14677 > URL: https://issues.apache.org/jira/browse/CAMEL-14677 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > We feature a swoosh on the front page of the website (the wavy lines > currently behind the "Camel 3.1 is here! what's new" text). > It would be interesting to see it incorporated in the rest of the website. > For example I think it would be nice to add it as a separator beneath the > main topmost navigation. And in that case perhaps not as a wavy line, but as > few narrow straight lines. > An interesting transition animation can be then done from the large swoosh > that's present now and fixed in place, to this separating lines just below > the topmost navigation. > Also see CAMEL-14676 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (CAMEL-14675) Feature avatars on the blog posts
[ https://issues.apache.org/jira/browse/CAMEL-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rashika Rathi updated CAMEL-14675: -- Comment: was deleted (was: [~zregvart] ok so how can i get the idea who's working is it mentioned somewhere which i'm missing or need to check every pull request ?) > Feature avatars on the blog posts > - > > Key: CAMEL-14675 > URL: https://issues.apache.org/jira/browse/CAMEL-14675 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > On the previous website we had avatars of the blog authors next to the blog > posts. We could utilize Gravatar or GitHub avatars. > Things to watch out for: > * existing blog posts don't have any pointers to avatars, so they might need > editing > * the website content security policy doesn't allow loading remote resources > (except for Algolia search), so images need to be downloaded and cached to be > served from the camel.apache.org domain or we need to allow loading images > from Gravatar or GitHub > One option could be using the [data > templates|https://gohugo.io/templates/data-templates/#call-the-functions-with-a-url] > in Hugo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14803) camel-karaf - Add docs for website
[ https://issues.apache.org/jira/browse/CAMEL-14803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068483#comment-17068483 ] Zoran Regvart commented on CAMEL-14803: --- I can work on adding Antora skeleton structure to the camel-karaf repository and I can create a PR to include it on the website. The content would be quite sparse based on the docs we currently have. > camel-karaf - Add docs for website > -- > > Key: CAMEL-14803 > URL: https://issues.apache.org/jira/browse/CAMEL-14803 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.2.0 > > > It would be good to have the docs setup for camel-karaf like we have for > camel-spring-boot, so we can build part for the website and have camel karaf > included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14803) camel-karaf - Add docs for website
Claus Ibsen created CAMEL-14803: --- Summary: camel-karaf - Add docs for website Key: CAMEL-14803 URL: https://issues.apache.org/jira/browse/CAMEL-14803 Project: Camel Issue Type: Task Reporter: Claus Ibsen Assignee: Zoran Regvart Fix For: 3.2.0 It would be good to have the docs setup for camel-karaf like we have for camel-spring-boot, so we can build part for the website and have camel karaf included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14675) Feature avatars on the blog posts
[ https://issues.apache.org/jira/browse/CAMEL-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068467#comment-17068467 ] Rashika Rathi commented on CAMEL-14675: --- [~zregvart] ok so how can i get the idea who's working is it mentioned somewhere which i'm missing or need to check every pull request ? > Feature avatars on the blog posts > - > > Key: CAMEL-14675 > URL: https://issues.apache.org/jira/browse/CAMEL-14675 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > On the previous website we had avatars of the blog authors next to the blog > posts. We could utilize Gravatar or GitHub avatars. > Things to watch out for: > * existing blog posts don't have any pointers to avatars, so they might need > editing > * the website content security policy doesn't allow loading remote resources > (except for Algolia search), so images need to be downloaded and cached to be > served from the camel.apache.org domain or we need to allow loading images > from Gravatar or GitHub > One option could be using the [data > templates|https://gohugo.io/templates/data-templates/#call-the-functions-with-a-url] > in Hugo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14675) Feature avatars on the blog posts
[ https://issues.apache.org/jira/browse/CAMEL-14675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068455#comment-17068455 ] Zoran Regvart commented on CAMEL-14675: --- Please note that we have [~avgupt] working on this in pull request at https://github.com/apache/camel-website/pull/210 > Feature avatars on the blog posts > - > > Key: CAMEL-14675 > URL: https://issues.apache.org/jira/browse/CAMEL-14675 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Minor > Labels: help-wanted > > On the previous website we had avatars of the blog authors next to the blog > posts. We could utilize Gravatar or GitHub avatars. > Things to watch out for: > * existing blog posts don't have any pointers to avatars, so they might need > editing > * the website content security policy doesn't allow loading remote resources > (except for Algolia search), so images need to be downloaded and cached to be > served from the camel.apache.org domain or we need to allow loading images > from Gravatar or GitHub > One option could be using the [data > templates|https://gohugo.io/templates/data-templates/#call-the-functions-with-a-url] > in Hugo. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13804) website - Add page which lists which components supports which runtimes
[ https://issues.apache.org/jira/browse/CAMEL-13804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068444#comment-17068444 ] Rashika Rathi commented on CAMEL-13804: --- hi [~davsclaus] can you guide me for this issue? > website - Add page which lists which components supports which runtimes > --- > > Key: CAMEL-13804 > URL: https://issues.apache.org/jira/browse/CAMEL-13804 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > With CAMEL-13803 we should have a catalog that knows which component support > which runtimes. > Then we can make a page with a table of each component with a matrix with [x] > for which they support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068436#comment-17068436 ] Aashna Jena commented on CAMEL-13780: - Okay thank you! I'll work on this. > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14800) Camel-GraphQL: Use a camel consumer to receive events from GraphQL subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-14800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14800: Estimated Complexity: Moderate (was: Unknown) > Camel-GraphQL: Use a camel consumer to receive events from GraphQL > subscriptions > > > Key: CAMEL-14800 > URL: https://issues.apache.org/jira/browse/CAMEL-14800 > Project: Camel > Issue Type: New Feature > Components: camel-graphql >Reporter: Hiram R. Chirino >Priority: Major > Fix For: 3.3.0 > > > In addition to Queries and Mutations, GraphQL, supports Subscriptions to > notify the client of events in GraphQL engine. These would map nicely to a > camel consumer endpoint so that you can use subscriptions to trigger EIP > processing in a camel route. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14800) Camel-GraphQL: Use a camel consumer to receive events from GraphQL subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-14800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14800: Priority: Major (was: Critical) > Camel-GraphQL: Use a camel consumer to receive events from GraphQL > subscriptions > > > Key: CAMEL-14800 > URL: https://issues.apache.org/jira/browse/CAMEL-14800 > Project: Camel > Issue Type: New Feature > Components: camel-graphql >Reporter: Hiram R. Chirino >Priority: Major > Fix For: 3.3.0 > > > In addition to Queries and Mutations, GraphQL, supports Subscriptions to > notify the client of events in GraphQL engine. These would map nicely to a > camel consumer endpoint so that you can use subscriptions to trigger EIP > processing in a camel route. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14772) website - Add section to display the 6 camel projects with logos
[ https://issues.apache.org/jira/browse/CAMEL-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068435#comment-17068435 ] Aashna Jena commented on CAMEL-14772: - Hi! Can I help on this? > website - Add section to display the 6 camel projects with logos > > > Key: CAMEL-14772 > URL: https://issues.apache.org/jira/browse/CAMEL-14772 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: front-page.png > > > We should take this tweet with screenshot, and put on the front page to > better highlight the Camel projects we have > https://twitter.com/ApacheCamel/status/1242074457050624000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14800) Camel-GraphQL: Use a camel consumer to receive events from GraphQL subscriptions
[ https://issues.apache.org/jira/browse/CAMEL-14800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14800: Fix Version/s: 3.3.0 > Camel-GraphQL: Use a camel consumer to receive events from GraphQL > subscriptions > > > Key: CAMEL-14800 > URL: https://issues.apache.org/jira/browse/CAMEL-14800 > Project: Camel > Issue Type: New Feature > Components: camel-graphql >Reporter: Hiram R. Chirino >Priority: Critical > Fix For: 3.3.0 > > > In addition to Queries and Mutations, GraphQL, supports Subscriptions to > notify the client of events in GraphQL engine. These would map nicely to a > camel consumer endpoint so that you can use subscriptions to trigger EIP > processing in a camel route. -- This message was sent by Atlassian Jira (v8.3.4#803005)
