[jira] [Commented] (CAMEL-14769) Responsive View - Wastage of screen real-estate on large displays
[ https://issues.apache.org/jira/browse/CAMEL-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065307#comment-17065307 ] Avishi Gupta commented on CAMEL-14769: -- I am working on this issue. > Responsive View - Wastage of screen real-estate on large displays > - > > Key: CAMEL-14769 > URL: https://issues.apache.org/jira/browse/CAMEL-14769 > Project: Camel > Issue Type: Bug > Components: website >Affects Versions: 3.x >Reporter: Praveen Kottarathil >Priority: Major > Labels: gsoc2020, help-wanted, outreachy2020 > Attachments: box-model.PNG, jmx-docs.PNG > > > I was looking at the JMX docs at > [https://camel.apache.org/manual/latest/jmx.html] > and noticed that the left and right margins for `article.doc` doesn't work > well on large screens and wastes quite a lot of available screen real estate > as shown in the screen shot (Test setup is a 4K display). Very likely this > impacts all pages and not just the JMX page. Just that it is very evident > here. > > !jmx-docs.PNG|width=1083,height=578! > > Extra attachment: Box model so that an assignee can get started quick. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14771) Consider using the master branch tooling for 2.x and 3.0.x catalog construction
[
https://issues.apache.org/jira/browse/CAMEL-14771?focusedWorklogId=408372=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408372
]
ASF GitHub Bot logged work on CAMEL-14771:
--
Author: ASF GitHub Bot
Created on: 23/Mar/20 22:47
Start Date: 23/Mar/20 22:47
Worklog Time Spent: 10m
Work Description: djencks commented on pull request #3669: resolves
CAMEL-14771: unambiguous property name and some more source info
URL: https://github.com/apache/camel/pull/3669
NEEDS REVIEW AND CONSIDERATION!
I've included:
- PrepareCatalogMojo.java change property name so it may be configured
(needed for use in 2.x branch). This also filters out some json files that
should not be processed but are located in the 2.x branch.
- a few catch-rethrow exceptions to add the file name of the problematic
resource. I needed these to figure out what was going wrong on the 2.x branch.
Is this a good idea?
Here's the configuration for the 2.x platforms/camel-catalog/pom.xml:
```
org.apache.camel
camel-package-maven-plugin
3.2.0-SNAPSHOT
prepare-catalog
prepare-user-guide
update-doc-component-list
prepare-parent-pom
prepare-release-pom
${project.build.directory}/../../../camel-core
process-resources
```
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: 408372)
Remaining Estimate: 0h
Time Spent: 10m
> Consider using the master branch tooling for 2.x and 3.0.x catalog
> construction
> ---
>
> Key: CAMEL-14771
> URL: https://issues.apache.org/jira/browse/CAMEL-14771
> Project: Camel
> Issue Type: Improvement
> Components: website
>Affects Versions: 3.1.0
>Reporter: David Jencks
>Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The 3.0.x branch includes the tooling needed to construct the components
> component index pages, but the 2.x branch does not. Some slight modification
> and configuration of the master branch tooling allow it to be used for the
> 2.x index pages. The modifications are roughly:
> * excluding some json files that are not intended for the catalog
> * changing some parameter names that are shared across mojos but have
> different meanings, so that they may be configured.
> I don't know if this is a good idea or not. I only changed the one name that
> conflicts, but if we decide to do this changing some more would be a good
> idea.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Work logged] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?focusedWorklogId=408365=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408365 ] ASF GitHub Bot logged work on CAMEL-14770: -- Author: ASF GitHub Bot Created on: 23/Mar/20 22:28 Start Date: 23/Mar/20 22:28 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3668: resolves CAMEL-14770: sort nav files by doc title case insensitive URL: https://github.com/apache/camel/pull/3668 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: 408365) Time Spent: 20m (was: 10m) > 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] [Work logged] (CAMEL-14770) Sort nav the same as index pages
[ https://issues.apache.org/jira/browse/CAMEL-14770?focusedWorklogId=408342=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408342 ] ASF GitHub Bot logged work on CAMEL-14770: -- Author: ASF GitHub Bot Created on: 23/Mar/20 21:37 Start Date: 23/Mar/20 21:37 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3668: resolves CAMEL-14770: sort nav files by doc title case insensitive URL: https://github.com/apache/camel/pull/3668 Adds sort method, shows the effect on nav files. 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: 408342) Remaining Estimate: 0h Time Spent: 10m > 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: 10m > 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-14771) Consider using the master branch tooling for 2.x and 3.0.x catalog construction
David Jencks created CAMEL-14771: Summary: Consider using the master branch tooling for 2.x and 3.0.x catalog construction Key: CAMEL-14771 URL: https://issues.apache.org/jira/browse/CAMEL-14771 Project: Camel Issue Type: Improvement Components: website Affects Versions: 3.1.0 Reporter: David Jencks Fix For: 3.2.0 The 3.0.x branch includes the tooling needed to construct the components component index pages, but the 2.x branch does not. Some slight modification and configuration of the master branch tooling allow it to be used for the 2.x index pages. The modifications are roughly: * excluding some json files that are not intended for the catalog * changing some parameter names that are shared across mojos but have different meanings, so that they may be configured. I don't know if this is a good idea or not. I only changed the one name that conflicts, but if we decide to do this changing some more would be a good idea. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14770) Sort nav the same as index pages
David Jencks created CAMEL-14770: Summary: 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 Fix For: 3.2.0 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-14766) Rearrange 3.0.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14766. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > Rearrange 3.0.x components component similar to latest > -- > > Key: CAMEL-14766 > URL: https://issues.apache.org/jira/browse/CAMEL-14766 > 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 > > Time Spent: 20m > Remaining Estimate: 0h > > Rearrange website source in the 3.0.x branch for the components component to > imitate 'latest' (master) branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14765) Rearrange 2.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks resolved CAMEL-14765. -- Fix Version/s: 3.2.0 Resolution: Fixed PR merged > Rearrange 2.x components component similar to latest > > > Key: CAMEL-14765 > URL: https://issues.apache.org/jira/browse/CAMEL-14765 > 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 > > Time Spent: 20m > Remaining Estimate: 0h > > Rearrange the website sources in the 2.x branch to imitate the components > component in the 'latest' (master) branch per CAMEL-14698Consider rearranging > site source to Antora norms -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14765) Rearrange 2.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14765?focusedWorklogId=408327=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408327 ] ASF GitHub Bot logged work on CAMEL-14765: -- Author: ASF GitHub Bot Created on: 23/Mar/20 21:22 Start Date: 23/Mar/20 21:22 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3667: resolves CAMEL-14765: rearrange components website sources to match 'latest' URL: https://github.com/apache/camel/pull/3667 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: 408327) Time Spent: 20m (was: 10m) > Rearrange 2.x components component similar to latest > > > Key: CAMEL-14765 > URL: https://issues.apache.org/jira/browse/CAMEL-14765 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Rearrange the website sources in the 2.x branch to imitate the components > component in the 'latest' (master) branch per CAMEL-14698Consider rearranging > site source to Antora norms -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14766) Rearrange 3.0.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14766?focusedWorklogId=408328=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408328 ] ASF GitHub Bot logged work on CAMEL-14766: -- Author: ASF GitHub Bot Created on: 23/Mar/20 21:22 Start Date: 23/Mar/20 21:22 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3666: Resolves CAMEL-14766: Rearrange component sources and automation to match latest. URL: https://github.com/apache/camel/pull/3666 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: 408328) Time Spent: 20m (was: 10m) > Rearrange 3.0.x components component similar to latest > -- > > Key: CAMEL-14766 > URL: https://issues.apache.org/jira/browse/CAMEL-14766 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Rearrange website source in the 3.0.x branch for the components component to > imitate 'latest' (master) branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14766) Rearrange 3.0.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065108#comment-17065108 ] David Jencks commented on CAMEL-14766: -- Preview at [https://camel-preview-1.s3-us-west-2.amazonaws.com/index.html] Beware, indexified urls in links don't work, you'll need to add the "index.html" yourself. > Rearrange 3.0.x components component similar to latest > -- > > Key: CAMEL-14766 > URL: https://issues.apache.org/jira/browse/CAMEL-14766 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Rearrange website source in the 3.0.x branch for the components component to > imitate 'latest' (master) branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14765) Rearrange 2.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065107#comment-17065107 ] David Jencks commented on CAMEL-14765: -- Preview at [https://camel-preview-1.s3-us-west-2.amazonaws.com/index.html] Beware, indexified urls in links don't work, you'll need to add the "index.html" yourself. > Rearrange 2.x components component similar to latest > > > Key: CAMEL-14765 > URL: https://issues.apache.org/jira/browse/CAMEL-14765 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Rearrange the website sources in the 2.x branch to imitate the components > component in the 'latest' (master) branch per CAMEL-14698Consider rearranging > site source to Antora norms -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14765) Rearrange 2.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14765?focusedWorklogId=408322=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408322 ] ASF GitHub Bot logged work on CAMEL-14765: -- Author: ASF GitHub Bot Created on: 23/Mar/20 21:16 Start Date: 23/Mar/20 21:16 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3667: resolves CAMEL-14765: rearrange components website sources to match 'latest' URL: https://github.com/apache/camel/pull/3667 This does not include all the automation used to construct the index pages; I'll open a separate issue/pr for that as I'm not sure it's a wise change. 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: 408322) Remaining Estimate: 0h Time Spent: 10m > Rearrange 2.x components component similar to latest > > > Key: CAMEL-14765 > URL: https://issues.apache.org/jira/browse/CAMEL-14765 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Rearrange the website sources in the 2.x branch to imitate the components > component in the 'latest' (master) branch per CAMEL-14698Consider rearranging > site source to Antora norms -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14766) Rearrange 3.0.x components component similar to latest
[ https://issues.apache.org/jira/browse/CAMEL-14766?focusedWorklogId=408320=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-408320 ] ASF GitHub Bot logged work on CAMEL-14766: -- Author: ASF GitHub Bot Created on: 23/Mar/20 21:12 Start Date: 23/Mar/20 21:12 Worklog Time Spent: 10m Work Description: djencks commented on pull request #3666: Resolves CAMEL-14766: Rearrange component sources and automation to match latest. URL: https://github.com/apache/camel/pull/3666 This rearranges the 3.0.x camel website sources for components to match the 'latest' version (master branch). 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: 408320) Remaining Estimate: 0h Time Spent: 10m > Rearrange 3.0.x components component similar to latest > -- > > Key: CAMEL-14766 > URL: https://issues.apache.org/jira/browse/CAMEL-14766 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: David Jencks >Assignee: David Jencks >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Rearrange website source in the 3.0.x branch for the components component to > imitate 'latest' (master) branch. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14769) Responsive View - Wastage of screen real-estate on large displays
[ https://issues.apache.org/jira/browse/CAMEL-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Kottarathil updated CAMEL-14769: Labels: gsoc2020 help-wanted outreachy2020 (was: gsoc2020 outreachy2020) > Responsive View - Wastage of screen real-estate on large displays > - > > Key: CAMEL-14769 > URL: https://issues.apache.org/jira/browse/CAMEL-14769 > Project: Camel > Issue Type: Bug > Components: website >Affects Versions: 3.x >Reporter: Praveen Kottarathil >Priority: Major > Labels: gsoc2020, help-wanted, outreachy2020 > Attachments: box-model.PNG, jmx-docs.PNG > > > I was looking at the JMX docs at > [https://camel.apache.org/manual/latest/jmx.html] > and noticed that the left and right margins for `article.doc` doesn't work > well on large screens and wastes quite a lot of available screen real estate > as shown in the screen shot (Test setup is a 4K display). Very likely this > impacts all pages and not just the JMX page. Just that it is very evident > here. > > !jmx-docs.PNG|width=1083,height=578! > > Extra attachment: Box model so that an assignee can get started quick. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14769) Responsive View - Wastage of screen real-estate on large displays
[ https://issues.apache.org/jira/browse/CAMEL-14769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Kottarathil updated CAMEL-14769: Description: I was looking at the JMX docs at [https://camel.apache.org/manual/latest/jmx.html] and noticed that the left and right margins for `article.doc` doesn't work well on large screens and wastes quite a lot of available screen real estate as shown in the screen shot (Test setup is a 4K display). Very likely this impacts all pages and not just the JMX page. Just that it is very evident here. !jmx-docs.PNG|width=1083,height=578! Extra attachment: Box model so that an assignee can get started quick. was: I was looking at the JMX docs at [https://camel.apache.org/manual/latest/jmx.html] and noticed that the left and right margins for `article.doc` doesn't work well on large screens and wastes quite a lot of available screen real estate as shown in the screen shot (Test setup is a 4K display). Very likely this impacts all pages and not just the JMX page. Just that it is very evident here. Extra attachment: Box model so that an assignee can get started quick. > Responsive View - Wastage of screen real-estate on large displays > - > > Key: CAMEL-14769 > URL: https://issues.apache.org/jira/browse/CAMEL-14769 > Project: Camel > Issue Type: Bug > Components: website >Affects Versions: 3.x >Reporter: Praveen Kottarathil >Priority: Major > Labels: gsoc2020, outreachy2020 > Attachments: box-model.PNG, jmx-docs.PNG > > > I was looking at the JMX docs at > [https://camel.apache.org/manual/latest/jmx.html] > and noticed that the left and right margins for `article.doc` doesn't work > well on large screens and wastes quite a lot of available screen real estate > as shown in the screen shot (Test setup is a 4K display). Very likely this > impacts all pages and not just the JMX page. Just that it is very evident > here. > > !jmx-docs.PNG|width=1083,height=578! > > Extra attachment: Box model so that an assignee can get started quick. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14769) Responsive View - Wastage of screen real-estate on large displays
Praveen Kottarathil created CAMEL-14769: --- Summary: Responsive View - Wastage of screen real-estate on large displays Key: CAMEL-14769 URL: https://issues.apache.org/jira/browse/CAMEL-14769 Project: Camel Issue Type: Bug Components: website Affects Versions: 3.x Reporter: Praveen Kottarathil Attachments: box-model.PNG, jmx-docs.PNG I was looking at the JMX docs at [https://camel.apache.org/manual/latest/jmx.html] and noticed that the left and right margins for `article.doc` doesn't work well on large screens and wastes quite a lot of available screen real estate as shown in the screen shot (Test setup is a 4K display). Very likely this impacts all pages and not just the JMX page. Just that it is very evident here. Extra attachment: Box model so that an assignee can get started quick. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14683) Fix logo display on responsive view
[ https://issues.apache.org/jira/browse/CAMEL-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Kottarathil closed CAMEL-14683. --- > Fix logo display on responsive view > --- > > Key: CAMEL-14683 > URL: https://issues.apache.org/jira/browse/CAMEL-14683 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Praveen Kottarathil >Priority: Minor > Labels: help-wanted > Attachments: Capture.PNG, > Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg, > image-2020-03-10-18-43-10-718.png, logo_hamburger-menu.png, > social-accounts.png > > > > Camel logo does not display properly in responsive view. As far as I > remember, this used to work in the past and could be a side effect from > recent changes. > Steps to reproduce on a device with bigger screen area > # Visit [https://camel.apache.org|https://camel.apache.org/] > # Switch to responsive view [Chrome how > to|https://developers.google.com/web/tools/chrome-devtools/device-mode] / > [Firefox how > to|https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode] > # Have a look at the top bar render > Alternate option to reproduce, visit the page on a mobile phone. Responsive > view on tablets may be OK. > Perhaps we can suppress display of social accounts and search bar in response > view. > Keep only Camel logo and the hamburger menu. > Screenshot from a real device below. > !Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg|width=250,height=520! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14683) Fix logo display on responsive view
[ https://issues.apache.org/jira/browse/CAMEL-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17065016#comment-17065016 ] Praveen Kottarathil edited comment on CAMEL-14683 at 3/23/20, 6:59 PM: --- Appears to have resolved. very likely with 8469acf7064d82d5ce13caf5a690b43cdfd8704e on github !Capture.PNG! was (Author: praveenkottarat...@gmail.com): Appears to have resolved. very likely with 8469acf7064d82d5ce13caf5a690b43cdfd8704e on github > Fix logo display on responsive view > --- > > Key: CAMEL-14683 > URL: https://issues.apache.org/jira/browse/CAMEL-14683 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Praveen Kottarathil >Priority: Minor > Labels: help-wanted > Attachments: Capture.PNG, > Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg, > image-2020-03-10-18-43-10-718.png, logo_hamburger-menu.png, > social-accounts.png > > > > Camel logo does not display properly in responsive view. As far as I > remember, this used to work in the past and could be a side effect from > recent changes. > Steps to reproduce on a device with bigger screen area > # Visit [https://camel.apache.org|https://camel.apache.org/] > # Switch to responsive view [Chrome how > to|https://developers.google.com/web/tools/chrome-devtools/device-mode] / > [Firefox how > to|https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode] > # Have a look at the top bar render > Alternate option to reproduce, visit the page on a mobile phone. Responsive > view on tablets may be OK. > Perhaps we can suppress display of social accounts and search bar in response > view. > Keep only Camel logo and the hamburger menu. > Screenshot from a real device below. > !Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg|width=250,height=520! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14683) Fix logo display on responsive view
[ https://issues.apache.org/jira/browse/CAMEL-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Kottarathil updated CAMEL-14683: Attachment: Capture.PNG > Fix logo display on responsive view > --- > > Key: CAMEL-14683 > URL: https://issues.apache.org/jira/browse/CAMEL-14683 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Praveen Kottarathil >Priority: Minor > Labels: help-wanted > Attachments: Capture.PNG, > Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg, > image-2020-03-10-18-43-10-718.png, logo_hamburger-menu.png, > social-accounts.png > > > > Camel logo does not display properly in responsive view. As far as I > remember, this used to work in the past and could be a side effect from > recent changes. > Steps to reproduce on a device with bigger screen area > # Visit [https://camel.apache.org|https://camel.apache.org/] > # Switch to responsive view [Chrome how > to|https://developers.google.com/web/tools/chrome-devtools/device-mode] / > [Firefox how > to|https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode] > # Have a look at the top bar render > Alternate option to reproduce, visit the page on a mobile phone. Responsive > view on tablets may be OK. > Perhaps we can suppress display of social accounts and search bar in response > view. > Keep only Camel logo and the hamburger menu. > Screenshot from a real device below. > !Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg|width=250,height=520! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14683) Fix logo display on responsive view
[ https://issues.apache.org/jira/browse/CAMEL-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Kottarathil resolved CAMEL-14683. - Resolution: Fixed Appears to have resolved. very likely with 8469acf7064d82d5ce13caf5a690b43cdfd8704e on github > Fix logo display on responsive view > --- > > Key: CAMEL-14683 > URL: https://issues.apache.org/jira/browse/CAMEL-14683 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Praveen Kottarathil >Priority: Minor > Labels: help-wanted > Attachments: > Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg, > image-2020-03-10-18-43-10-718.png, logo_hamburger-menu.png, > social-accounts.png > > > > Camel logo does not display properly in responsive view. As far as I > remember, this used to work in the past and could be a side effect from > recent changes. > Steps to reproduce on a device with bigger screen area > # Visit [https://camel.apache.org|https://camel.apache.org/] > # Switch to responsive view [Chrome how > to|https://developers.google.com/web/tools/chrome-devtools/device-mode] / > [Firefox how > to|https://developer.mozilla.org/en-US/docs/Tools/Responsive_Design_Mode] > # Have a look at the top bar render > Alternate option to reproduce, visit the page on a mobile phone. Responsive > view on tablets may be OK. > Perhaps we can suppress display of social accounts and search bar in response > view. > Keep only Camel logo and the hamburger menu. > Screenshot from a real device below. > !Screenshot_2020-03-09-15-42-39-326_com.android.chrome.jpg|width=250,height=520! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-13704) Add github pull request template for PR instruction
[
https://issues.apache.org/jira/browse/CAMEL-13704?focusedWorklogId=407975=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407975
]
ASF GitHub Bot logged work on CAMEL-13704:
--
Author: ASF GitHub Bot
Created on: 23/Mar/20 15:26
Start Date: 23/Mar/20 15:26
Worklog Time Spent: 10m
Work Description: Xxyumi-hub commented on pull request #3665: CAMEL-13704
- Added PR template file with instructions on what to include when subm…
URL: https://github.com/apache/camel/pull/3665
CAMEL-13704 -
https://issues.apache.org/jira/projects/CAMEL/issues/CAMEL-13704?filter=allopenissues
I have created a PR template file for this repo and plan to add the same
template to camel-k and camel-quarkus
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: 407975)
Remaining Estimate: 0h
Time Spent: 10m
> Add github pull request template for PR instruction
> ---
>
> Key: CAMEL-13704
> URL: https://issues.apache.org/jira/browse/CAMEL-13704
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Willem Jiang
>Priority: Major
> Labels: help-wanted
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It's standard procedure to accept the big contribution with iCLA granted in
> ASF.
> We should list this information when the contributor send the PR by
> specifying a PR template for github. It could be annoying for the
> experienced contributors, but it could save us some time for the new
> contributors.
> Here is a draft I have, please add comment for it.
> {code}
> - [ ] 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.
> - [ ] 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` in your module to make sure basic checks pass.
> A more thorough check will be performed on your pull request automatically.
> - [ ] If this contribution is large, please file an Apache [Individual
> Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14715) Move karaf/osgi to separate git repositor
[ https://issues.apache.org/jira/browse/CAMEL-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064846#comment-17064846 ] Jean-Baptiste Onofré commented on CAMEL-14715: -- [~davsclaus] thanks, let me take a look ;) > Move karaf/osgi to separate git repositor > - > > Key: CAMEL-14715 > URL: https://issues.apache.org/jira/browse/CAMEL-14715 > Project: Camel > Issue Type: Improvement > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 3.2.0 > > > See > https://camel.465427.n5.nabble.com/Moving-Karaf-OSGi-code-into-a-Camel-sub-project-td5859320.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14715) Move karaf/osgi to separate git repositor
[ https://issues.apache.org/jira/browse/CAMEL-14715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064844#comment-17064844 ] Claus Ibsen commented on CAMEL-14715: - [ERROR] Failed to execute goal org.apache.camel:camel-eip-documentation-enricher-maven-plugin:3.2.0-SNAPSHOT:eip-documentation-enricher (eip-documentation-enricher) on project camel-blueprint: camelCoreDir does not exist -> [Help 1] camel-blueprit ^^^ > Move karaf/osgi to separate git repositor > - > > Key: CAMEL-14715 > URL: https://issues.apache.org/jira/browse/CAMEL-14715 > Project: Camel > Issue Type: Improvement > Components: karaf, osgi >Reporter: Claus Ibsen >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 3.2.0 > > > See > https://camel.465427.n5.nabble.com/Moving-Karaf-OSGi-code-into-a-Camel-sub-project-td5859320.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14751) add icons and rearrange the camel front page functionality section
[ https://issues.apache.org/jira/browse/CAMEL-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064802#comment-17064802 ] gunkev commented on CAMEL-14751: This also increase user experience > add icons and rearrange the camel front page functionality section > -- > > Key: CAMEL-14751 > URL: https://issues.apache.org/jira/browse/CAMEL-14751 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.0.0 >Reporter: gunkev >Priority: Trivial > Labels: improvement > Attachments: Screenshot from 2020-03-18 20-25-25.png > > Original Estimate: 1h > Remaining Estimate: 1h > > I order to make he front page of camel website look more appeal and > understandable some illustrations or icons should be added in order to > reflect the subject matter of the functionalities section -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14751) add icons and rearrange the camel front page functionality section
[ https://issues.apache.org/jira/browse/CAMEL-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064801#comment-17064801 ] gunkev commented on CAMEL-14751: [~zregvart] What I mean here is to attract user attention with some illustrations or Icons. In the packed with functionality section in the home, I proposed that instead of just writing text also we actually provides icons with reflect each functionalities so we get both textual as well as illustrative language. > add icons and rearrange the camel front page functionality section > -- > > Key: CAMEL-14751 > URL: https://issues.apache.org/jira/browse/CAMEL-14751 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.0.0 >Reporter: gunkev >Priority: Trivial > Labels: improvement > Attachments: Screenshot from 2020-03-18 20-25-25.png > > Original Estimate: 1h > Remaining Estimate: 1h > > I order to make he front page of camel website look more appeal and > understandable some illustrations or icons should be added in order to > reflect the subject matter of the functionalities section -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14750) rearrange elements after the packed with functionalities section in the front of the website
[ https://issues.apache.org/jira/browse/CAMEL-14750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064798#comment-17064798 ] gunkev commented on CAMEL-14750: [~zregvart] what is mean is to re-classify each camel project in the project section found on the frontpage. I think the font-size for the camel project is too big and The alignment could be better. Here is the issue in question [https://github.com/apache/camel-website/pull/250] > rearrange elements after the packed with functionalities section in the front > of the website > > > Key: CAMEL-14750 > URL: https://issues.apache.org/jira/browse/CAMEL-14750 > Project: Camel > Issue Type: Improvement > Components: website > Environment: linux or window or android >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Fix For: Future > > Attachments: Screenshot from 2020-03-20 14-16-36.png > > Original Estimate: 2h > Remaining Estimate: 2h > > Some elements in the frontpage of the camel website are not really good to > see and read it will be good to arrange those element in order to make look > more good and readable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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=17064789#comment-17064789 ] JyotiAttri commented on CAMEL-14567: [~RimshaCh], Ok > 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-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=17064782#comment-17064782 ] Rimsha Chaudhry commented on CAMEL-14567: - [~jyotiattri] hi , I am already working on this ,just don't want that we duplicate work.I am rearranging the sidebar as listed in the comment and description above. > 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-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=17064777#comment-17064777 ] Rimsha Chaudhry commented on CAMEL-14567: - [~zregvart] thankyou for the help. > 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-11522) Include requirements
[ https://issues.apache.org/jira/browse/CAMEL-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064775#comment-17064775 ] Rimsha Chaudhry commented on CAMEL-11522: - Yes I realized that ,and I removed the dependencies from requirements > Include requirements > > > Key: CAMEL-11522 > URL: https://issues.apache.org/jira/browse/CAMEL-11522 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: Include Requirement.png > > > We should have a requirements page, a getting started page, or what version > page, that lists, at least, JVM versions per Camel version required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (CAMEL-14710) Camel-Jcache: Tests are failing
[ https://issues.apache.org/jira/browse/CAMEL-14710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitry Volodin reassigned CAMEL-14710: -- Assignee: Dmitry Volodin > Camel-Jcache: Tests are failing > --- > > Key: CAMEL-14710 > URL: https://issues.apache.org/jira/browse/CAMEL-14710 > Project: Camel > Issue Type: Test > Components: camel-jcache >Reporter: Andrea Cosentino >Assignee: Dmitry Volodin >Priority: Major > Fix For: 3.2.0 > > > It should be related to hazelcast update. [~Madhawa Gunasekara], please have > a look. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14767) Camel-website: Build is broken
[ https://issues.apache.org/jira/browse/CAMEL-14767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14767. -- Resolution: Fixed > Camel-website: Build is broken > -- > > Key: CAMEL-14767 > URL: https://issues.apache.org/jira/browse/CAMEL-14767 > Project: Camel > Issue Type: Bug >Reporter: Andrea Cosentino >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > *11:04:10* $ link-checker --disable-external --mkdocs --allow-hash-href > public*11:05:07* page not found from > components/latest/eips/enterprise-integration-patterns.html to > components/latest/eips/_attachments/Hohpe_EIP_camel_20150622.zip*11:05:07* > page not found from > components/latest/eips/enterprise-integration-patterns.html to > components/latest/eips/_attachments/Hohpe_EIP_camel_OpenOffice.zip*11:05:07* > page not found from community/articles/index.html to > manual/latest/enterprise-integration-patterns.html > > David, can you please have a look, this looks to be related to your last > commits -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (CAMEL-14752) Unmarshal TAR w/ error handling in Camel 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Omar Al-Safi closed CAMEL-14752. Resolution: Fixed > Unmarshal TAR w/ error handling in Camel 3.x > > > Key: CAMEL-14752 > URL: https://issues.apache.org/jira/browse/CAMEL-14752 > Project: Camel > Issue Type: Bug > Components: camel-tarfile >Affects Versions: 3.0.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14752) Unmarshal TAR w/ error handling in Camel 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14752?focusedWorklogId=407844=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407844 ] ASF GitHub Bot logged work on CAMEL-14752: -- Author: ASF GitHub Bot Created on: 23/Mar/20 11:16 Start Date: 23/Mar/20 11:16 Worklog Time Spent: 10m Work Description: omarsmak commented on pull request #3664: CAMEL-14752: Throw an exception on corrupted tarfiles URL: https://github.com/apache/camel/pull/3664 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: 407844) Time Spent: 20m (was: 10m) > Unmarshal TAR w/ error handling in Camel 3.x > > > Key: CAMEL-14752 > URL: https://issues.apache.org/jira/browse/CAMEL-14752 > Project: Camel > Issue Type: Bug > Components: camel-tarfile >Affects Versions: 3.0.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14752) Unmarshal TAR w/ error handling in Camel 3.x
[ https://issues.apache.org/jira/browse/CAMEL-14752?focusedWorklogId=407843=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407843 ] ASF GitHub Bot logged work on CAMEL-14752: -- Author: ASF GitHub Bot Created on: 23/Mar/20 11:14 Start Date: 23/Mar/20 11:14 Worklog Time Spent: 10m Work Description: omarsmak commented on pull request #3664: CAMEL-14752: Throw an exception on corrupted tarfiles URL: https://github.com/apache/camel/pull/3664 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: 407843) Remaining Estimate: 0h Time Spent: 10m > Unmarshal TAR w/ error handling in Camel 3.x > > > Key: CAMEL-14752 > URL: https://issues.apache.org/jira/browse/CAMEL-14752 > Project: Camel > Issue Type: Bug > Components: camel-tarfile >Affects Versions: 3.0.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[
https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064708#comment-17064708
]
Zoran Regvart commented on CAMEL-13812:
---
{quote}I suggest changing Getting started for Getting started with Apache Camel
and deleting Longer Getting Started Guide.{quote}
Not sure about renaming, "Getting started" to "Getting started with Apache
Camel", and about deleting the "Longer Getting Started Guide", what's the value
in that?
{quote}In Documentation (after Summary and Overview) I would suggest the
following order:{quote}
I don't think it makes much sense to keep any of that, the navigation on the
left should be used to access content. We have an issue on making sure that the
linked pages are also available on the navigation (CAMEL-13780).
I like the direction this is heading, especially with the splitting of FAQ into
a separate component/module. Make sure to read Antora documentation on that,
and that you're aware of the {{xref}} link changes that need to be made when
the split is done.
> Split up user manual
>
>
> Key: CAMEL-13812
> URL: https://issues.apache.org/jira/browse/CAMEL-13812
> Project: Camel
> Issue Type: Sub-task
> Components: documentation, website
>Reporter: Zoran Regvart
>Priority: Major
> Labels: help-wanted
> Fix For: 3.x
>
> Attachments: FAQ landing-page.docx,
> getting-started-with-apache-camel.docx
>
>
> I think we would benefit from splitting up the user manual into even smaller
> Antora modules:
> * FAQ
> * Getting started
> * User manual
> Perhaps (not sure), Architecture. I think grouping of pages would help as we
> could have a landing (index) page for each module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (CAMEL-14751) add icons and rearrange the camel front page functionality section
[ https://issues.apache.org/jira/browse/CAMEL-14751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart closed CAMEL-14751. - Please create an issue with more thorough description on the problem you see and the proposed solution. I'm closing this in lieu of that. > add icons and rearrange the camel front page functionality section > -- > > Key: CAMEL-14751 > URL: https://issues.apache.org/jira/browse/CAMEL-14751 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.0.0 >Reporter: gunkev >Priority: Trivial > Labels: improvement > Attachments: Screenshot from 2020-03-18 20-25-25.png > > Original Estimate: 1h > Remaining Estimate: 1h > > I order to make he front page of camel website look more appeal and > understandable some illustrations or icons should be added in order to > reflect the subject matter of the functionalities section -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14750) rearrange elements after the packed with functionalities section in the front of the website
[ https://issues.apache.org/jira/browse/CAMEL-14750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14750: -- Affects Version/s: (was: 3.1.0) > rearrange elements after the packed with functionalities section in the front > of the website > > > Key: CAMEL-14750 > URL: https://issues.apache.org/jira/browse/CAMEL-14750 > Project: Camel > Issue Type: Improvement > Environment: linux or window or android >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Fix For: Future > > Attachments: Screenshot from 2020-03-20 14-16-36.png > > Original Estimate: 2h > Remaining Estimate: 2h > > Some elements in the frontpage of the camel website are not really good to > see and read it will be good to arrange those element in order to make look > more good and readable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14750) rearrange elements after the packed with functionalities section in the front of the website
[ https://issues.apache.org/jira/browse/CAMEL-14750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14750: -- Labels: help-wanted (was: improve improvement) > rearrange elements after the packed with functionalities section in the front > of the website > > > Key: CAMEL-14750 > URL: https://issues.apache.org/jira/browse/CAMEL-14750 > Project: Camel > Issue Type: Improvement >Affects Versions: 3.1.0 > Environment: linux or window or android >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Fix For: Future > > Attachments: Screenshot from 2020-03-20 14-16-36.png > > Original Estimate: 2h > Remaining Estimate: 2h > > Some elements in the frontpage of the camel website are not really good to > see and read it will be good to arrange those element in order to make look > more good and readable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14750) rearrange elements after the packed with functionalities section in the front of the website
[ https://issues.apache.org/jira/browse/CAMEL-14750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064701#comment-17064701 ] Zoran Regvart commented on CAMEL-14750: --- [~Gunkev] can you explain what do you mean with some elements and what are you proposing here as a solution? > rearrange elements after the packed with functionalities section in the front > of the website > > > Key: CAMEL-14750 > URL: https://issues.apache.org/jira/browse/CAMEL-14750 > Project: Camel > Issue Type: Improvement > Components: website > Environment: linux or window or android >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Fix For: Future > > Attachments: Screenshot from 2020-03-20 14-16-36.png > > Original Estimate: 2h > Remaining Estimate: 2h > > Some elements in the frontpage of the camel website are not really good to > see and read it will be good to arrange those element in order to make look > more good and readable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14750) rearrange elements after the packed with functionalities section in the front of the website
[ https://issues.apache.org/jira/browse/CAMEL-14750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14750: -- Component/s: website > rearrange elements after the packed with functionalities section in the front > of the website > > > Key: CAMEL-14750 > URL: https://issues.apache.org/jira/browse/CAMEL-14750 > Project: Camel > Issue Type: Improvement > Components: website > Environment: linux or window or android >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Fix For: Future > > Attachments: Screenshot from 2020-03-20 14-16-36.png > > Original Estimate: 2h > Remaining Estimate: 2h > > Some elements in the frontpage of the camel website are not really good to > see and read it will be good to arrange those element in order to make look > more good and readable -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14718) Improve the designing of the front-page of Apache Camel Website
[ https://issues.apache.org/jira/browse/CAMEL-14718?focusedWorklogId=407813=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-407813 ] ASF GitHub Bot logged work on CAMEL-14718: -- Author: ASF GitHub Bot Created on: 23/Mar/20 10:05 Start Date: 23/Mar/20 10:05 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #221: CAMEL-14718: add the push down hover effect to the buttons in frontpage URL: https://github.com/apache/camel-website/pull/221 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: 407813) Time Spent: 40m (was: 0.5h) > Improve the designing of the front-page of Apache Camel Website > --- > > Key: CAMEL-14718 > URL: https://issues.apache.org/jira/browse/CAMEL-14718 > Project: Camel > Issue Type: Improvement >Reporter: Aemie >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > In the front-page of the website, under the camel section, on change of > screen width, the title and buttons are center-aligned except the text. Thus > to make the text center-aligned so that it looks neat. > Another thing is that for the buttons when hovered, there is an outer-glow > and in smaller screen-width for multiple buttons, the glow overlaps. Hence, > create a good hover button affect. Refer [link creative button hover > effects.|https://tympanus.net/Development/CreativeButtons/] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[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=17064683#comment-17064683 ] JyotiAttri commented on CAMEL-14567: Hi [~zregvart], I want to work on this issue but shows error. For this, I need to change in [https://github.com/apache/camel-quarkus/blob/c34d83e81524df1289ca659cc4a7955de04c78ce/docs/antora.yml#L19]. So after changing the text, I was trying to build the repository to run the tests. For that, I need to install maven but when I am running this command in Powershell it shows error. Please help me, if I am wrong then tell me. I have asked this error in Gitter chat also but no reply there. > 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-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=17064677#comment-17064677 ] Zoran Regvart commented on CAMEL-14567: --- >From the description this looks like an issue in this menu: !Screenshot_2020-03-23 Apache Camel user manual - Apache Camel.png! That can be accessed bottom left. Those are component names in Antora terminology and they need to be changed, as described in the [comment above|https://issues.apache.org/jira/browse/CAMEL-14567?focusedCommentId=17047443=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17047443]. > 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] [Updated] (CAMEL-14567) camel-website - Sidebar menu tidy up names
[ https://issues.apache.org/jira/browse/CAMEL-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14567: -- Attachment: Screenshot_2020-03-23 Apache Camel user manual - Apache Camel.png > 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-13800) Mobile usability issues reported in Google search console
[ https://issues.apache.org/jira/browse/CAMEL-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064674#comment-17064674 ] JyotiAttri commented on CAMEL-13800: [~zregvart], Thanks > Mobile usability issues reported in Google search console > - > > Key: CAMEL-13800 > URL: https://issues.apache.org/jira/browse/CAMEL-13800 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Attachments: Screenshot_2019-07-29 Mobile Usability.png, > cxf_component_mobile_screenshot.png > > > Google search console reports issues in mobile usability: > * Clickable elements too close together > * Text too small to read > * Content wider than screen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14725) center elements vertically in the navbar
[ https://issues.apache.org/jira/browse/CAMEL-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14725: -- Estimated Complexity: Novice (was: Moderate) > center elements vertically in the navbar > > > Key: CAMEL-14725 > URL: https://issues.apache.org/jira/browse/CAMEL-14725 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Attachments: Screenshot from 2020-03-16 17-31-36.png > > Original Estimate: 1h > Remaining Estimate: 1h > > Elements in the navigation bar are slightly downward. some line-height or any > other method should be applied in order to center the elements vertically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14725) center elements vertically in the navbar
[ https://issues.apache.org/jira/browse/CAMEL-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14725: -- Labels: help-wanted (was: improve) > center elements vertically in the navbar > > > Key: CAMEL-14725 > URL: https://issues.apache.org/jira/browse/CAMEL-14725 > Project: Camel > Issue Type: Improvement > Components: website >Affects Versions: 3.1.0 >Reporter: gunkev >Priority: Trivial > Labels: help-wanted > Attachments: Screenshot from 2020-03-16 17-31-36.png > > Original Estimate: 1h > Remaining Estimate: 1h > > Elements in the navigation bar are slightly downward. some line-height or any > other method should be applied in order to center the elements vertically. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14709) Make sure that the website can be built in Windows
[
https://issues.apache.org/jira/browse/CAMEL-14709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064656#comment-17064656
]
Zoran Regvart commented on CAMEL-14709:
---
[~Aemie] should be fine if your changes don't prevent us from building on Unix
machines and on the build server.
> Make sure that the website can be built in Windows
> --
>
> Key: CAMEL-14709
> URL: https://issues.apache.org/jira/browse/CAMEL-14709
> Project: Camel
> Issue Type: Task
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
> Labels: help-wanted
>
> Right now we [run the hugo
> build|https://github.com/apache/camel-website/blob/21dbd4d74b5f0270a697e8de300eeff30dca14dd/package.json#L6]
> from a npm/yarn script.
> This includes the {{--cacheDir}} parameter which specifies where Hugo puts
> cached data, e.g. data fetched via {{getJSON}}.
> When we build the website on the build server we wish to take advantage of
> previously cached data, and to do that we [set the {{HUGO_CACHE_DIR}}
> environment
> variable|https://github.com/apache/camel-website/blob/21dbd4d74b5f0270a697e8de300eeff30dca14dd/Jenkinsfile#L41].
> The shell interpolation used: {{${HUGO_CACHE_DIR:-$(pwd)/.hugo_data}}} makes
> sure that if {{HUGO_CACHE_DIR}} is not defined {{.hugo_data}} in current
> directory is used instead.
> This doesn't work on Windows as it relies on Unix shell variable
> interpolation.
> We need a solution that has the same functionality, i.e. we can specify the
> cache directory via {{HUGO_CACHE_DIR}} environment variable and if the
> {{HUGO_CACHE_DIR}} variable is not set use {{.hugo_data}} in current
> directory, but works on both Unix and Windows systems.
> I think there could be a way to use some cross platform npm packages to do
> this intended to be used in scripts; or we could create a helper JavaScript
> file for this and invoke hugo binary from it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-11522) Include requirements
[ https://issues.apache.org/jira/browse/CAMEL-11522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064653#comment-17064653 ] Zoran Regvart commented on CAMEL-11522: --- [~RimshaCh] I would not list dependencies I would list requirements. Java version primarily, and versions of platforms Camel runs on: Spring/Spring Boot, Karaf, Kubernetes/OpenShift. > Include requirements > > > Key: CAMEL-11522 > URL: https://issues.apache.org/jira/browse/CAMEL-11522 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: Include Requirement.png > > > We should have a requirements page, a getting started page, or what version > page, that lists, at least, JVM versions per Camel version required. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13800) Mobile usability issues reported in Google search console
[
https://issues.apache.org/jira/browse/CAMEL-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064648#comment-17064648
]
Zoran Regvart commented on CAMEL-13800:
---
[~jyotiattri] look for {{HEADER.html}} pages under
[static/schema|https://github.com/apache/camel-website/tree/master/static/schema].
> Mobile usability issues reported in Google search console
> -
>
> Key: CAMEL-13800
> URL: https://issues.apache.org/jira/browse/CAMEL-13800
> Project: Camel
> Issue Type: Sub-task
> Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
> Attachments: Screenshot_2019-07-29 Mobile Usability.png,
> cxf_component_mobile_screenshot.png
>
>
> Google search console reports issues in mobile usability:
> * Clickable elements too close together
> * Text too small to read
> * Content wider than screen
--
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=17064646#comment-17064646
]
Zoran Regvart commented on CAMEL-13780:
---
{quote}Hi, let me get this straight. I should look at all the links present in
this wiki page and this manual. I should find out which of these links are not
present in the new manual and add those links here?{quote}
This issue is about making changes to {{nav.adoc}} in the user manual. About
listing all pages we currently have in the user manual, that might not be
linked from {{nav.adoc}} and grouping the content so the pages are not listed
but grouped by topics. Some of the pages seem to be linked only from
{{index.adoc}} and not from {{nav.adoc}}. We had something similar on the wiki
and published as PDF.
Here's an [archive.org PDF version of the
manual|https://web.archive.org/web/2018113738/http://camel.apache.org/manual/camel-manual-2.11.0.pdf],
to illustrate what we need, albeit updated and as a set of web pages.
> 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] [Commented] (CAMEL-14744) camel-salesforce : lazy-login
[
https://issues.apache.org/jira/browse/CAMEL-14744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17064639#comment-17064639
]
Zoran Regvart commented on CAMEL-14744:
---
[~MaartenTutak] not sure if that was intended. If think {{lazy-login}} should
be also considered in all cases. Sounds like you're already have an idea of
what needs to change, perhaps you can create a pull request for the change?
> camel-salesforce : lazy-login
> -
>
> Key: CAMEL-14744
> URL: https://issues.apache.org/jira/browse/CAMEL-14744
> Project: Camel
> Issue Type: Bug
> Components: camel-salesforce
>Affects Versions: 3.1.0
>Reporter: Maarten Tutak
>Priority: Minor
>
> I'm using org.apache.camel.springboot:camel-salesforce-starter:3.1.0
> Configuration *camel.component.salesforce.lazy-login* only seems to work when
> it's used in combination with
> *camel.component.salesforce.lazy-start-producer*.
> When used on it's own, method
>
> *_org.apache.camel.component.salesforce.internal.client.AbstractClientBase#start()_*
> will call method
> _*org.apache.camel.component.salesforce.internal.SalesforceSession#login()*_
> without an appropriate guard statement.
> Is this intended behaviour?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=17064623#comment-17064623
]
Gerald Kallas commented on CAMEL-14629:
---
[~jbonofre] do you have any news in between? Client is still waiting for a
solution .. many thanks in advance.
Gerald
> 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: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 3.1.1
>
>
> 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:
