date:20200306



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643
 ] 

Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 6:44 PM:
--

Hi Zoran,

I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you tell me which webpage this link should navigate to? And what 
should be the content of that webpage?

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file (this is 
how building.md is displayed in public/docs/building/index.html)? Or should it 
direct to a webpage like /manual/latest/getting-started.html etc? I also need 
some idea about what should be the content of this file.

The Documentation tab in the navbar has 10 links in the drop-down as of now. 
Each page has several more links, which is a little confusing for the user. 
Should we think of reorganising this after we add API documentation?


was (Author: aashnajena):
Hi Zoran,

I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you tell me which webpage this link should navigate to? And what 
should be the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file (this is 
how building.md is displayed in public/docs/building/index.html)? Or should it 
direct to a webpage like /manual/latest/getting-started.html etc? Also, please 
tell me what should be the content of api.md

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (CAMEL-14669) Upgrade mockito to 3.3.x

2020-03-06 Thread ASF GitHub Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/CAMEL-14669?focusedWorklogId=399291=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-399291
 ]

ASF GitHub Bot logged work on CAMEL-14669:
--

Author: ASF GitHub Bot
Created on: 06/Mar/20 18:43
Start Date: 06/Mar/20 18:43
Worklog Time Spent: 10m 
  Work Description: madhawa-gunasekara commented on pull request #3614: 
CAMEL-14669 Upgrade mockito to 3.3.1
URL: https://github.com/apache/camel/pull/3614
 
 
   
 

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: 399291)
Remaining Estimate: 0h
Time Spent: 10m

> Upgrade mockito to 3.3.x
> 
>
> Key: CAMEL-14669
> URL: https://issues.apache.org/jira/browse/CAMEL-14669
> Project: Camel
>  Issue Type: Task
>Reporter: Claus Ibsen
>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-13754) Site documentation improvements

2020-03-06 Thread Rimsha Chaudhry (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053689#comment-17053689
 ] 

Rimsha Chaudhry commented on CAMEL-13754:
-

Thankyou [~zregvart] for the guidance.I'll surely follow the guidelines.

> Site documentation improvements
> ---
>
> Key: CAMEL-13754
> URL: https://issues.apache.org/jira/browse/CAMEL-13754
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.x
>
>
> Some of the pages are blank or nearly empty on the website for instance:
> * [Camel-k landing page|https://camel.apache.org/staging/projects/camel-k/]
> * [components reference landing 
> page|https://camel.apache.org/staging/components/latest/]
> The user [manual landing 
> page|https://camel.apache.org/staging/manual/latest/] could also be improved 
> to offer an introduction to Camel not just a list of chapters.



--
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

2020-03-06 Thread Devkant Gorai (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-14677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053684#comment-17053684
 ] 

Devkant Gorai commented on CAMEL-14677:
---

Hello [~zregvart] I am Devkant Gorai,I am an Outreachy applicant.I too think 
there must be a swoosh design in the website.I went through your expected 
swoosh design at 
https://camel.apache.org/blog/Camel3-Whatsnew/camel3-website.png
.  
I can definitely work on this if you assign me.
I have few questions :-

1)Will be static or animated?
2)will you provide me the .png/.svg files of the animated line? or will I have 
to design it myself?

But for now if you assign me the task I can straightaway start working on "few 
narrow straight lines" that you expect to be placed under the main topmost 
navbar.

This is my very first proposal under the outreachy contribution process.Please 
if you like my working plan.You are always free to assign me and guide me as 
per your ease.Thank You.

> 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] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643
 ] 

Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 6:33 PM:
--

Hi Zoran,

I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you tell me which webpage this link should navigate to? And what 
should be the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file (this is 
how building.md is displayed in public/docs/building/index.html)? Or should it 
direct to a webpage like /manual/latest/getting-started.html etc? Also, please 
tell me what should be the content of api.md


was (Author: aashnajena):
Hi Zoran,

I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you tell me which webpage this link should navigate to? And what 
should be the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file? Or 
should it direct to a webpage like /manual/latest/getting-started.html etc? 
Also, please tell me what should be the content of api.md

 

 

!camel_website.png! . Where s 

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
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

2020-03-06 Thread Luana Faustini (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-14677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053648#comment-17053648
 ] 

Luana Faustini commented on CAMEL-14677:


Hi [~zregvart] can I help with this issue? What is the next step? I have 
already installed node.js and yarn on my computer. Let me know if I can be 
useful here :) Thanks!

> 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] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643
 ] 

Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 5:55 PM:
--

Hi Zoran,

I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you tell me which webpage this link should navigate to? And what 
should be the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file? Or 
should it direct to a webpage like /manual/latest/getting-started.html etc? 
Also, please tell me what should be the content of api.md

 

 

!camel_website.png! . Where s 


was (Author: aashnajena):
Hi Zoran,



I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you which webpage this link should navigate to? And what should be 
the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file? Or 
should it direct to a webpage like /manual/latest/getting-started.html etc? 
Also, please tell me what should be the content of api.md

 

 

!camel_website.png! . Where s 

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643
 ] 

Aashna Jena commented on CAMEL-13902:
-

Hi Zoran,



I have added a block similar to 
[https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com]
 

I am able to display the option "API Documentation" in the menu now (see 
image). Can you which webpage this link should navigate to? And what should be 
the content of that webpage?

 

Your comment above says that this menu option should point to api.md file. 
Should this menu option direct to the GitHub page with the api.md file? Or 
should it direct to a webpage like /manual/latest/getting-started.html etc? 
Also, please tell me what should be the content of api.md

 

 

!camel_website.png! . Where s 

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work logged] (CAMEL-14646) [camel-azure] Add the possibility to set credentials as query parameters

2020-03-06 Thread ASF GitHub Bot (Jira)



 [ 
https://issues.apache.org/jira/browse/CAMEL-14646?focusedWorklogId=399262=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-399262
 ]

ASF GitHub Bot logged work on CAMEL-14646:
--

Author: ASF GitHub Bot
Created on: 06/Mar/20 17:50
Start Date: 06/Mar/20 17:50
Worklog Time Spent: 10m 
  Work Description: luigidemasi commented on pull request #3613: 
CAMEL-14646: [camel-azure] Add the possibility to set credentials as …
URL: https://github.com/apache/camel/pull/3613
 
 
   …query parameters
 

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: 399262)
Remaining Estimate: 0h
Time Spent: 10m

> [camel-azure] Add the possibility to set credentials as query parameters
> 
>
> Key: CAMEL-14646
> URL: https://issues.apache.org/jira/browse/CAMEL-14646
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-azure
>Reporter: Luigi De Masi
>Assignee: Luigi De Masi
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> On both blob and queue, add the possibility to set credentials as query 
> parameters on URI, like in AWS S3:
> {code}
> azure-blob://camelazure/container1/blobBlock?credentialsAccountName==y
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14679) Support DROP_ROOT_MODE in XStream JSON dataformat

2020-03-06 Thread Peter Palaga (Jira)

Peter Palaga created CAMEL-14679:


 Summary: Support DROP_ROOT_MODE in XStream JSON dataformat 
 Key: CAMEL-14679
 URL: https://issues.apache.org/jira/browse/CAMEL-14679
 Project: Camel
  Issue Type: Improvement
  Components: camel-xstream
Reporter: Peter Palaga


It is currently not possible to configure 
{{org.apache.camel.dataformat.xstream.JsonDataFormat}} to produce standard JSON 
without the XStream specific root node.

XStream JSON with root node:
{code:json}
{"org.apache.camel.quarkus.component.xstream.it.PojoA\:{"name":"Joe"}}{code}

Standard JSON:
{code:json}
{"name":"Joe"}{code}

With plain Xstream this can be reached via (see 
https://x-stream.github.io/json-tutorial.html#json-dropping-root )

{code:java}
XStream xstream = new XStream(new JsonHierarchicalStreamDriver() {
public HierarchicalStreamWriter createWriter(Writer writer) {
return new JsonWriter(writer, JsonWriter.DROP_ROOT_MODE);
}
});
{code}

But I have not found a way to configure the 
{{org.apache.camel.dataformat.xstream.JsonDataFormat}} in that way. So we 
probably need some change to allow this.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14634) documentation - Add page about endpoint-dsl and component-dsl to user guide



 [ 
https://issues.apache.org/jira/browse/CAMEL-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-14634:
--
Labels: help-wanted  (was: )

> documentation - Add page about endpoint-dsl and component-dsl to user guide
> ---
>
> Key: CAMEL-14634
> URL: https://issues.apache.org/jira/browse/CAMEL-14634
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation, website
>Reporter: Claus Ibsen
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.2.0
>
>
> We need to document the cool new features of endpoint-dsl and component-dsl 
> better. We should have a page for each of them, and added to the user guide
> [https://camel.apache.org/manual/latest/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14678) Find a way to version Camel Quarkus within the camel-quarkus repository

Zoran Regvart created CAMEL-14678:
-

 Summary: Find a way to version Camel Quarkus within the 
camel-quarkus repository
 Key: CAMEL-14678
 URL: https://issues.apache.org/jira/browse/CAMEL-14678
 Project: Camel
  Issue Type: Improvement
  Components: website
Reporter: Zoran Regvart


When we publish the Camel Quarkus documentation we reference a version of Camel 
Quarkus stored in an Asciidoc attribute in the camel-website repository. So 
each time we release Camel Quarkus we also need to update the camel-website 
repository to have the version correctly reflected in the published website. 
Have a look at the [recent pull 
request|https://github.com/apache/camel-website/pull/169] to increase this 
version.

A better solution would be to find a way to store that attribute within the 
camel-quarkus repository so it's independent of the website; or to have that 
version pulled in from the [GitHub 
releases|https://developer.github.com/v3/repos/releases/#get-the-latest-release]
 and incorporate it via Antora extension (have a look at the existing Antora 
[extensions we 
have|https://github.com/apache/camel-website/tree/master/extensions]).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13881) Article containers right margin is larger than left margin



[ 
https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053565#comment-17053565
 ] 

Zoran Regvart commented on CAMEL-13881:
---

To surmise the discussion relating to this issue. This issue was discussed on 
GitHub previously in [#94|http://example.com], 
[#107|https://github.com/apache/camel-website/pull/107] and most recently in 
[#167|https://github.com/apache/camel-website/pull/167] and here in a comment 
from [~smile_outreachy].

I don't think we fully understand what the best option to go forward here is. 
Do we allow the text to be in the _wide_ format by default, do we leave it in 
the narrow format and center the text. I think we need to research this and 
find out what option would be the best with regards to readability and design 
aesthetics. 

For everyone interested in their first contribution to Camel, you can also have 
a look at some easy to get started issues like CAMEL-14675, CAMEL-14674, 
CAMEL-14676 or CAMEL-14677. Look for issues relating to the {{website}} 
component with Novice complexity for other issues that might interest you 
(follow [this 
link|https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20website%20AND%20cf%5B12310060%5D%20%3D%20Novice%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC]
 for the filtered issues).

> Article containers right margin is larger than left margin
> --
>
> Key: CAMEL-13881
> URL: https://issues.apache.org/jira/browse/CAMEL-13881
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Antonin Stefanutti
>Priority: Minor
>  Labels: help-wanted
> Attachments: Screenshot 2019-08-20 at 10.51.48.png
>
>
> The right margin of the article containers is larger than the left margin. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14677) Incorporate the swoosh design element in the rest of the website

Zoran Regvart created CAMEL-14677:
-

 Summary: 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


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] [Created] (CAMEL-14676) Make the swoosh animation a bit more apparent

Zoran Regvart created CAMEL-14676:
-

 Summary: Make the swoosh animation a bit more apparent
 Key: CAMEL-14676
 URL: https://issues.apache.org/jira/browse/CAMEL-14676
 Project: Camel
  Issue Type: Improvement
  Components: website
Reporter: Zoran Regvart


I often need to point out to folk that the swoosh wavy lines at the top of the 
Camel website, currently behind the _Camel 3.1 is here! what's new_ text is 
animated.

I would be interested in seeing if folk think that the animation is needed, and 
if it is, how can it be improved.

For example, to make it more apparent it could be animated more vigorously when 
the visitor first arrives on the front page, and less vigorously on next visits.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13754) Site documentation improvements



[ 
https://issues.apache.org/jira/browse/CAMEL-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053499#comment-17053499
 ] 

Zoran Regvart commented on CAMEL-13754:
---

Hi [~RimshaCh] of course, and thank you for having an interest in contributing 
to Apache Camel.

Here are some guidelines on how to best approach the Apache Camel community and 
how to best apply yourself.

1. Communication

Apache Camel is an Apache Software Foundation project, all communication is 
done in the open on the project mailing lists.

You can read more on the reasoning behind this to get a better understanding of:

https://www.apache.org/foundation/mailinglists.html

All communication is subject to the ASF Code of Conduct, which you can read 
here:

https://www.apache.org/foundation/policies/conduct.html

For questions and guidance around contributing subscribe to the developer's 
mailing list by sending an e-mail to dev-subscr...@camel.apache.org.

We can also be reached on the Gitter chat at 
https://gitter.im/apache/apache-camel/.

We track issues using ASF Jira located at:

https://issues.apache.org/jira/browse/CAMEL

Where we maintain a list of issues that are easy to get started with, so you 
can familiarize yourself with the process and get your first contribution in:

https://issues.apache.org/jira/issues/?filter=12348073

And some areas that we are actively looking for help on:

https://issues.apache.org/jira/issues/?filter=12348074

When you're ready to contribute create a Pull request to one of the Camel 
projects you can find under the Apache organization on GitHub:

https://github.com/apache?q=camel

Expect that your Pull request will receive a review and that you will need to 
respond and correspond to that via comments at GitHub.

2. Getting started

Read the "Contributing to Apache Camel" document on the Camel website:

https://camel.apache.org/manual/latest/contributing.html

Identify areas you can contribute first. You don't have to be an expert in an 
area, the Apache Camel developers are available to offer help and guidance.

Introduce yourself on the developer's mailing list (see above), tell us what 
area of work or problem you wish to address in Camel. Create a draft of your 
solution, this can be simple 1-2 sentences on the change you wish to make. Try 
to be as specific as you can: include a short description of your intent, what 
you tried and what didn't work, or what you need help with. The best way of 
approaching the developers is by describing what you would like to work on and 
asking specific questions on how to get started. We'll do our best to guide you 
and help you make your contribution. 

We also participate in Google Summer of Code and Outreachy programs, for 
information about those look at those program websites. If you wish to 
participate in either of those follow the guidelines and schedule set by those 
programs. If you're unsure please reach out via official communication channels 
of those programs, or ask on the developer's mailing list for help.

3. Your first contribution

Make sure you followed the steps and guidelines outlined above. For bigger 
changes, make sure that you have discussed on the developer's mailing list or 
in the Jira issue tracker before hand. We love receiving contributions, to get 
the best response make sure that the reasoning behind the contribution you wish 
to make is clear: outline the problem and explain your solution for it.

Make sure you follow the guidelines outlined in the "Contributing to Apache 
Camel" document. Be respectful of the source checks, formatting and the 
structure of the git commit message we abide by. This will help you in getting 
your contribution accepted. Outline any changes you made but are unaware or 
unsure of any consequences or side effects.

Stay engaged, follow and respond to comments or questions you might be asked.

With that I wish you all the best and please do have fun while contributing to 
Apache Camel, we certainly do :)

> Site documentation improvements
> ---
>
> Key: CAMEL-13754
> URL: https://issues.apache.org/jira/browse/CAMEL-13754
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.x
>
>
> Some of the pages are blank or nearly empty on the website for instance:
> * [Camel-k landing page|https://camel.apache.org/staging/projects/camel-k/]
> * [components reference landing 
> page|https://camel.apache.org/staging/components/latest/]
> The user [manual landing 
> page|https://camel.apache.org/staging/manual/latest/] could also be improved 
> to offer an introduction to Camel not just a list of chapters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13894) Pull contributor data from JSON APIs



[ 
https://issues.apache.org/jira/browse/CAMEL-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053497#comment-17053497
 ] 

Zoran Regvart commented on CAMEL-13894:
---

Hi [~CynthiaOmovoiye] First of all, thank you for having an interest in 
contributing to Apache Camel.

Here are some guidelines on how to best approach the Apache Camel community and 
how to best apply yourself.

1. Communication

Apache Camel is an Apache Software Foundation project, all communication is 
done in the open on the project mailing lists.

You can read more on the reasoning behind this to get a better understanding of:

https://www.apache.org/foundation/mailinglists.html

All communication is subject to the ASF Code of Conduct, which you can read 
here:

https://www.apache.org/foundation/policies/conduct.html

For questions and guidance around contributing subscribe to the developer's 
mailing list by sending an e-mail to dev-subscr...@camel.apache.org.

We can also be reached on the Gitter chat at 
https://gitter.im/apache/apache-camel/.

We track issues using ASF Jira located at:

https://issues.apache.org/jira/browse/CAMEL

Where we maintain a list of issues that are easy to get started with, so you 
can familiarize yourself with the process and get your first contribution in:

https://issues.apache.org/jira/issues/?filter=12348073

And some areas that we are actively looking for help on:

https://issues.apache.org/jira/issues/?filter=12348074

When you're ready to contribute create a Pull request to one of the Camel 
projects you can find under the Apache organization on GitHub:

https://github.com/apache?q=camel

Expect that your Pull request will receive a review and that you will need to 
respond and correspond to that via comments at GitHub.

2. Getting started

Read the "Contributing to Apache Camel" document on the Camel website:

https://camel.apache.org/manual/latest/contributing.html

Identify areas you can contribute first. You don't have to be an expert in an 
area, the Apache Camel developers are available to offer help and guidance.

Introduce yourself on the developer's mailing list (see above), tell us what 
area of work or problem you wish to address in Camel. Create a draft of your 
solution, this can be simple 1-2 sentences on the change you wish to make. Try 
to be as specific as you can: include a short description of your intent, what 
you tried and what didn't work, or what you need help with. The best way of 
approaching the developers is by describing what you would like to work on and 
asking specific questions on how to get started. We'll do our best to guide you 
and help you make your contribution. 

We also participate in Google Summer of Code and Outreachy programs, for 
information about those look at those program websites. If you wish to 
participate in either of those follow the guidelines and schedule set by those 
programs. If you're unsure please reach out via official communication channels 
of those programs, or ask on the developer's mailing list for help.

3. Your first contribution

Make sure you followed the steps and guidelines outlined above. For bigger 
changes, make sure that you have discussed on the developer's mailing list or 
in the Jira issue tracker before hand. We love receiving contributions, to get 
the best response make sure that the reasoning behind the contribution you wish 
to make is clear: outline the problem and explain your solution for it.

Make sure you follow the guidelines outlined in the "Contributing to Apache 
Camel" document. Be respectful of the source checks, formatting and the 
structure of the git commit message we abide by. This will help you in getting 
your contribution accepted. Outline any changes you made but are unaware or 
unsure of any consequences or side effects.

Stay engaged, follow and respond to comments or questions you might be asked.

With that I wish you all the best and please do have fun while contributing to 
Apache Camel, we certainly do :)

> Pull contributor data from JSON APIs
> 
>
> Key: CAMEL-13894
> URL: https://issues.apache.org/jira/browse/CAMEL-13894
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Minor
>  Labels: help-wanted
>
> Hugo has a feature where we can [pull in data from JSON 
> APIs|https://gohugo.io/templates/data-templates/#call-the-functions-with-a-url]
>  we could use this feature to have a dynamic contributors page where we show 
> names and avatars from GitHub of all contributors to Camel.
> I think we could also have pull in data from Whimsy as JSON for PMC members 
> and commiters.
> This way we would not need to update contributors manually.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14634) documentation - Add page about endpoint-dsl and component-dsl to user guide



 [ 
https://issues.apache.org/jira/browse/CAMEL-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-14634:
--
Component/s: website

> documentation - Add page about endpoint-dsl and component-dsl to user guide
> ---
>
> Key: CAMEL-14634
> URL: https://issues.apache.org/jira/browse/CAMEL-14634
> Project: Camel
>  Issue Type: Improvement
>  Components: documentation, website
>Reporter: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> We need to document the cool new features of endpoint-dsl and component-dsl 
> better. We should have a page for each of them, and added to the user guide
> [https://camel.apache.org/manual/latest/]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053493#comment-17053493
 ] 

Zoran Regvart commented on CAMEL-13902:
---

Hi [~aashnajena] of course, feel free to familiarize yourself with the website 
from the [README|https://github.com/apache/camel-website/blob/master/README.md] 
we have and how to get started in contributing from our [contribution 
guide|https://camel.apache.org/manual/latest/contributing.html].

I think we can start by publishing the documentation for the camel-spi. I am a 
bit worried that the big menus we currently have reflect poorly on the 
usability of the site. I think we could use also some ideas in this area on how 
to best organize and present all the documentation we have.

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14675) Feature avatars on the blog posts

Zoran Regvart created CAMEL-14675:
-

 Summary: 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


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] [Updated] (CAMEL-14674) Nicer table design for the blog post



 [ 
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-14674:
--
Labels: help-wanted  (was: )

> Nicer table design for the blog post
> 
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
>  Issue Type: Improvement
>  Components: website
>Reporter: Zoran Regvart
>Priority: Minor
>  Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule 
> - Apache Camel.png
>
>
> We recently published a blog post that featured a HTML table. See how 
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be 
> centered had nicer padding and odd/even row distinction.
>  The changes would need to go to [antora-ui-camel/src/css/blog.css] and be 
> scoped to the blog section via CSS {{.blog}} class to prevent possible 
> collisions with the Antora generated documentation and CSS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (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
 ]

Zoran Regvart updated CAMEL-14675:
--
Labels: help-wanted  (was: )

> 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] [Created] (CAMEL-14674) Nicer table design for the blog post

Zoran Regvart created CAMEL-14674:
-

 Summary: Nicer table design for the blog post
 Key: CAMEL-14674
 URL: https://issues.apache.org/jira/browse/CAMEL-14674
 Project: Camel
  Issue Type: Improvement
  Components: website
Reporter: Zoran Regvart
 Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule 
- Apache Camel.png

We recently published a blog post that featured a HTML table. See how 
[https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:

!Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!

The design of the table could be a bit nicer, for example it could be centered 
had nicer padding and odd/even row distinction.

 The changes would need to go to [antora-ui-camel/src/css/blog.css] and be 
scoped to the blog section via CSS {{.blog}} class to prevent possible 
collisions with the Antora generated documentation and CSS.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website



[ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053461#comment-17053461
 ] 

Aashna Jena commented on CAMEL-13902:
-

Hi! Can I take up this issue? I'm looking at all the links given the comments 
above and I'd love to make my first contribution to the Camel website

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14668) camel-core - Optimize getEndpoint on camel context



[ 
https://issues.apache.org/jira/browse/CAMEL-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053448#comment-17053448
 ] 

Claus Ibsen commented on CAMEL-14668:
-

TODO: Optimize double encoding in DefaultComponent if uri is fast parsed (its 
safe already)

> camel-core - Optimize getEndpoint on camel context
> --
>
> Key: CAMEL-14668
> URL: https://issues.apache.org/jira/browse/CAMEL-14668
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> We can optimize this a bit, and also remove the weird support for endpoints 
> without context-paths.
> And we can avoid some double encoding if the uri can be fast parsed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14672) Invoke ComponentCustomizer as part of component initialization



[ 
https://issues.apache.org/jira/browse/CAMEL-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053442#comment-17053442
 ] 

Luca Burgazzoli commented on CAMEL-14672:
-

The same behaviour can be achieved by leverage 
_LifecycleStrategy::onComponentAdd_ but a dedicated interface would make it 
easier to customize components without having to deal with too many internals, 
as example once can then do something like:

{code:java}
@BindToRegistry
public static ComponentCustomizer s3Configurer() {
return component -> component.setSomething(...);
}
{code}

> Invoke ComponentCustomizer as part of component initialization
> --
>
> Key: CAMEL-14672
> URL: https://issues.apache.org/jira/browse/CAMEL-14672
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.2.0
>
>
> Camel has the concept of _ComponentCustomizer_ which is currently used only 
> by spring-boot starters and I wonder if we can make it a generic concept so 
> basically after configuring the component with properties, we should search 
> for customizers in the camel registry and apply them to the component itself.
> Examples:
> -  
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java
> - 
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (CAMEL-14672) Invoke ComponentCustomizer as part of component initialization



[ 
https://issues.apache.org/jira/browse/CAMEL-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053442#comment-17053442
 ] 

Luca Burgazzoli edited comment on CAMEL-14672 at 3/6/20, 2:03 PM:
--

The same behaviour can be achieved by leverage 
_LifecycleStrategy::onComponentAdd_ but a dedicated interface would make it 
easier to customize components without having to deal with too many internals, 
as example a user can then do something like:

{code:java}
@BindToRegistry
public static ComponentCustomizer s3Configurer() {
return component -> component.setSomething(...);
}
{code}


was (Author: lb):
The same behaviour can be achieved by leverage 
_LifecycleStrategy::onComponentAdd_ but a dedicated interface would make it 
easier to customize components without having to deal with too many internals, 
as example once can then do something like:

{code:java}
@BindToRegistry
public static ComponentCustomizer s3Configurer() {
return component -> component.setSomething(...);
}
{code}

> Invoke ComponentCustomizer as part of component initialization
> --
>
> Key: CAMEL-14672
> URL: https://issues.apache.org/jira/browse/CAMEL-14672
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.2.0
>
>
> Camel has the concept of _ComponentCustomizer_ which is currently used only 
> by spring-boot starters and I wonder if we can make it a generic concept so 
> basically after configuring the component with properties, we should search 
> for customizers in the camel registry and apply them to the component itself.
> Examples:
> -  
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java
> - 
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14672) Invoke ComponentCustomizer as part of component initialization



 [ 
https://issues.apache.org/jira/browse/CAMEL-14672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-14672:

Priority: Major  (was: Minor)

> Invoke ComponentCustomizer as part of component initialization
> --
>
> Key: CAMEL-14672
> URL: https://issues.apache.org/jira/browse/CAMEL-14672
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.2.0
>
>
> Camel has the concept of _ComponentCustomizer_ which is currently used only 
> by spring-boot starters and I wonder if we can make it a generic concept so 
> basically after configuring the component with properties, we should search 
> for customizers in the camel registry and apply them to the component itself.
> Examples:
> -  
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java
> - 
> https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13894) Pull contributor data from JSON APIs

2020-03-06 Thread Cynthia Omovoiye (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-13894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053440#comment-17053440
 ] 

Cynthia Omovoiye commented on CAMEL-13894:
--

Hi, I am Cynthia Omovoiye. I an outreachy applicant and I would like to 
contribute to this project. Please, how do I get started?

> Pull contributor data from JSON APIs
> 
>
> Key: CAMEL-13894
> URL: https://issues.apache.org/jira/browse/CAMEL-13894
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Minor
>  Labels: help-wanted
>
> Hugo has a feature where we can [pull in data from JSON 
> APIs|https://gohugo.io/templates/data-templates/#call-the-functions-with-a-url]
>  we could use this feature to have a dynamic contributors page where we show 
> names and avatars from GitHub of all contributors to Camel.
> I think we could also have pull in data from Whimsy as JSON for PMC members 
> and commiters.
> This way we would not need to update contributors manually.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14668) camel-core - Optimize getEndpoint on camel context



[ 
https://issues.apache.org/jira/browse/CAMEL-14668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053435#comment-17053435
 ] 

Claus Ibsen commented on CAMEL-14668:
-

We can also optimize the endpoint-dsl as well

> camel-core - Optimize getEndpoint on camel context
> --
>
> Key: CAMEL-14668
> URL: https://issues.apache.org/jira/browse/CAMEL-14668
> Project: Camel
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> We can optimize this a bit, and also remove the weird support for endpoints 
> without context-paths.
> And we can avoid some double encoding if the uri can be fast parsed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13754) Site documentation improvements

2020-03-06 Thread Rimsha Chaudhry (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053433#comment-17053433
 ] 

Rimsha Chaudhry commented on CAMEL-13754:
-

Hey , I am Rimsha , Got to know about this project through Outreachy. Can I 
work on this issue?

> Site documentation improvements
> ---
>
> Key: CAMEL-13754
> URL: https://issues.apache.org/jira/browse/CAMEL-13754
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.x
>
>
> Some of the pages are blank or nearly empty on the website for instance:
> * [Camel-k landing page|https://camel.apache.org/staging/projects/camel-k/]
> * [components reference landing 
> page|https://camel.apache.org/staging/components/latest/]
> The user [manual landing 
> page|https://camel.apache.org/staging/manual/latest/] could also be improved 
> to offer an introduction to Camel not just a list of chapters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14670) @PropertyInject : support for complex - non primitive - injection



 [ 
https://issues.apache.org/jira/browse/CAMEL-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-14670:

Priority: Minor  (was: Major)

> @PropertyInject : support for complex - non primitive - injection
> -
>
> Key: CAMEL-14670
> URL: https://issues.apache.org/jira/browse/CAMEL-14670
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 3.2.0
>
>
> Camel has a @PropertyInject annotation that works for primitives but it would 
> be nice to support complex objects so that one can write:
> {code:java}
> @BindToRegistry
> public static AmazonS3 minioClient(
> @PropertyInject("minio") MinioConfig config) {
> var endpoint = new 
> AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
> var credentials = new BasicAWSCredentials(config.getAccessKey(), 
> config.getSecretKey());
> var credentialsProvider = new AWSStaticCredentialsProvider(credentials);
> return AmazonS3ClientBuilder
> .standard()
> .withEndpointConfiguration(endpoint)
> .withCredentials(credentialsProvider)
> .withPathStyleAccessEnabled(true)
> .build();
> }
> {code}
> And have _minio_ interpreted as properties root so that users can define 
> properties like:
> {code}
> minio.address = http://my-minio.com
> minio.access-key = ...
> minio.secret-key = ...
> {code}
> And receive a _MinioConfig_ object configured from those options as method 
> parameter.
> As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
> combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I 
> think it would be nice to support such case too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14670) @PropertyInject : support for complex - non primitive - injection



[ 
https://issues.apache.org/jira/browse/CAMEL-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053429#comment-17053429
 ] 

Luca Burgazzoli commented on CAMEL-14670:
-

Depending of the type of the _@PropertyInject_ target, we may have a number of 
strategies:

- if it is an interface we can generate synthetic implementation
- if there is a _configurer_ we could use it to bind properties without the 
need of reflection and fall-back to reflective configuration in case a 
_configurer_ is not available
- we can use APT or a maven plugin to generate the _configurer_ 

> @PropertyInject : support for complex - non primitive - injection
> -
>
> Key: CAMEL-14670
> URL: https://issues.apache.org/jira/browse/CAMEL-14670
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.2.0
>
>
> Camel has a @PropertyInject annotation that works for primitives but it would 
> be nice to support complex objects so that one can write:
> {code:java}
> @BindToRegistry
> public static AmazonS3 minioClient(
> @PropertyInject("minio") MinioConfig config) {
> var endpoint = new 
> AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
> var credentials = new BasicAWSCredentials(config.getAccessKey(), 
> config.getSecretKey());
> var credentialsProvider = new AWSStaticCredentialsProvider(credentials);
> return AmazonS3ClientBuilder
> .standard()
> .withEndpointConfiguration(endpoint)
> .withCredentials(credentialsProvider)
> .withPathStyleAccessEnabled(true)
> .build();
> }
> {code}
> And have _minio_ interpreted as properties root so that users can define 
> properties like:
> {code}
> minio.address = http://my-minio.com
> minio.access-key = ...
> minio.secret-key = ...
> {code}
> And receive a _MinioConfig_ object configured from those options as method 
> parameter.
> As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
> combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I 
> think it would be nice to support such case too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-13812) Split up user manual



 [ 
https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-13812:
--
Estimated Complexity: Novice  (was: Unknown)

> 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
>
>
> 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] [Created] (CAMEL-14673) Split model / runtime

2020-03-06 Thread Guillaume Nodet (Jira)

Guillaume Nodet created CAMEL-14673:
---

 Summary: Split model / runtime
 Key: CAMEL-14673
 URL: https://issues.apache.org/jira/browse/CAMEL-14673
 Project: Camel
  Issue Type: Task
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 3.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-13704) Add github pull request template for PR instruction



 [ 
https://issues.apache.org/jira/browse/CAMEL-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-13704:
--
Estimated Complexity: Novice  (was: Unknown)

> 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
>
> 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] [Updated] (CAMEL-13902) Publish links to JavaDoc on the website



 [ 
https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-13902:
--
Estimated Complexity: Novice  (was: Unknown)

> Publish links to JavaDoc on the website
> ---
>
> Key: CAMEL-13902
> URL: https://issues.apache.org/jira/browse/CAMEL-13902
> Project: Camel
>  Issue Type: Task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> We can utilize javadoc.io to publish the JavaDoc for:
> * camel-api
> * camel-support
> * camel-util



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (CAMEL-13975) Feature early releases on the website



 [ 
https://issues.apache.org/jira/browse/CAMEL-13975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-13975.
---
  Assignee: Zoran Regvart
Resolution: Implemented

> Feature early releases on the website
> -
>
> Key: CAMEL-13975
> URL: https://issues.apache.org/jira/browse/CAMEL-13975
> Project: Camel
>  Issue Type: Improvement
>  Components: website
>Reporter: Zoran Regvart
>Assignee: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> Currently if we create a new release-note it will push older releases. So for 
> RC1 we didn't create one. As a solution we could add an attribute 
> `early-access: true` to the release note and have it not push out other 
> releases.
> That way it can also be featured in a separate early access section on the 
> releases/downloads page.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-13754) Site documentation improvements



 [ 
https://issues.apache.org/jira/browse/CAMEL-13754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-13754:
--
Estimated Complexity: Novice  (was: Unknown)

> Site documentation improvements
> ---
>
> Key: CAMEL-13754
> URL: https://issues.apache.org/jira/browse/CAMEL-13754
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
> Fix For: 3.x
>
>
> Some of the pages are blank or nearly empty on the website for instance:
> * [Camel-k landing page|https://camel.apache.org/staging/projects/camel-k/]
> * [components reference landing 
> page|https://camel.apache.org/staging/components/latest/]
> The user [manual landing 
> page|https://camel.apache.org/staging/manual/latest/] could also be improved 
> to offer an introduction to Camel not just a list of chapters.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14672) Invoke ComponentCustomizer as part of component initialization

Luca Burgazzoli created CAMEL-14672:
---

 Summary: Invoke ComponentCustomizer as part of component 
initialization
 Key: CAMEL-14672
 URL: https://issues.apache.org/jira/browse/CAMEL-14672
 Project: Camel
  Issue Type: New Feature
  Components: camel-core
Reporter: Luca Burgazzoli
 Fix For: 3.2.0


Camel has the concept of _ComponentCustomizer_ which is currently used only by 
spring-boot starters and I wonder if we can make it a generic concept so 
basically after configuring the component with properties, we should search for 
customizers in the camel registry and apply them to the component itself.

Examples:
-  
https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java
- 
https://github.com/apache/camel-spring-boot/blob/master/components-starter/camel-ehcache-starter/src/main/java/org/apache/camel/component/ehcache/springboot/EhcacheComponentAutoConfiguration.java





--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14671) Make PropertiesFunction part of the PropertiesComponent SPI

Luca Burgazzoli created CAMEL-14671:
---

 Summary: Make PropertiesFunction part of the PropertiesComponent 
SPI
 Key: CAMEL-14671
 URL: https://issues.apache.org/jira/browse/CAMEL-14671
 Project: Camel
  Issue Type: Improvement
  Components: camel-core, camel-properties
Reporter: Luca Burgazzoli
 Fix For: 3.2.0


The properties component support _PropertiesFunction_ but those are not exposed 
as a SPI and the _PropertiesComponent_ SPI does not have methods to add them.

It would be nice to make  _PropertiesFunction_  part of the  
_PropertiesComponent_ SPI



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14670) @PropertyInject : support for complex - non primitive - injection



 [ 
https://issues.apache.org/jira/browse/CAMEL-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-14670:

Description: 
Camel has a @PropertyInject annotation that works for primitives but it would 
be nice to support complex objects so that one can write:

{code:java}
@BindToRegistry
public static AmazonS3 minioClient(
@PropertyInject("minio") MinioConfig config) {

var endpoint = new 
AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
var credentials = new BasicAWSCredentials(config.getAccessKey(), 
config.getSecretKey());
var credentialsProvider = new AWSStaticCredentialsProvider(credentials);

return AmazonS3ClientBuilder
.standard()
.withEndpointConfiguration(endpoint)
.withCredentials(credentialsProvider)
.withPathStyleAccessEnabled(true)
.build();
}
{code}

And have _minio_ interpreted as properties root so that users can define 
properties like:

{code}
minio.address = http://my-minio.com
minio.access-key = ...
minio.secret-key = ...
{code}

And receive an _MinioConfig_ object configured from those options as method 
parameter.

As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I think 
it would be nice to support such case too.





  was:
Camel has a @PropertyInject annotation that works for primitives but it would 
be nice to support complex objects so that one can write:

{code:java}
@BindToRegistry
public static AmazonS3 minioClient(
@PropertyInject("minio") MinioConfig config) {

var endpoint = new 
AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
var credentials = new BasicAWSCredentials(config.getAccessKey(), 
config.getSecretKey());
var credentialsProvider = new AWSStaticCredentialsProvider(credentials);

return AmazonS3ClientBuilder
.standard()
.withEndpointConfiguration(endpoint)
.withCredentials(credentialsProvider)
.withPathStyleAccessEnabled(true)
.build();
}
{code}

And have _minio_ interpreted as properties root so that once can define 
properties like:

{code}
minio.address = http://my-minio.com
minio.access-key = ...
minio.secret-key = ...
{code}

And receive an _MinioConfig_ object configured from those options as method 
parameter.

As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I think 
it would be nice to support such case too.






> @PropertyInject : support for complex - non primitive - injection
> -
>
> Key: CAMEL-14670
> URL: https://issues.apache.org/jira/browse/CAMEL-14670
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.2.0
>
>
> Camel has a @PropertyInject annotation that works for primitives but it would 
> be nice to support complex objects so that one can write:
> {code:java}
> @BindToRegistry
> public static AmazonS3 minioClient(
> @PropertyInject("minio") MinioConfig config) {
> var endpoint = new 
> AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
> var credentials = new BasicAWSCredentials(config.getAccessKey(), 
> config.getSecretKey());
> var credentialsProvider = new AWSStaticCredentialsProvider(credentials);
> return AmazonS3ClientBuilder
> .standard()
> .withEndpointConfiguration(endpoint)
> .withCredentials(credentialsProvider)
> .withPathStyleAccessEnabled(true)
> .build();
> }
> {code}
> And have _minio_ interpreted as properties root so that users can define 
> properties like:
> {code}
> minio.address = http://my-minio.com
> minio.access-key = ...
> minio.secret-key = ...
> {code}
> And receive an _MinioConfig_ object configured from those options as method 
> parameter.
> As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
> combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I 
> think it would be nice to support such case too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14670) @PropertyInject : support for complex - non primitive - injection

Luca Burgazzoli created CAMEL-14670:
---

 Summary: @PropertyInject : support for complex - non primitive - 
injection
 Key: CAMEL-14670
 URL: https://issues.apache.org/jira/browse/CAMEL-14670
 Project: Camel
  Issue Type: New Feature
  Components: camel-core
Reporter: Luca Burgazzoli
 Fix For: 3.2.0


Camel has a @PropertyInject annotation that works for primitives but it would 
be nice to support complex objects so that one can write:

{code:java}
@BindToRegistry
public static AmazonS3 minioClient(
@PropertyInject("minio") MinioConfig config) {

var endpoint = new 
AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
var credentials = new BasicAWSCredentials(config.getAccessKey(), 
config.getSecretKey());
var credentialsProvider = new AWSStaticCredentialsProvider(credentials);

return AmazonS3ClientBuilder
.standard()
.withEndpointConfiguration(endpoint)
.withCredentials(credentialsProvider)
.withPathStyleAccessEnabled(true)
.build();
}
{code}

And have _minio_ interpreted as properties root so that once can define 
properties like:

{code}
minio.address = http://my-minio.com
minio.access-key = ...
minio.secret-key = ...
{code}

And receive an _MinioConfig_ object configured from those options as method 
parameter.

As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I think 
it would be nice to support such case too.







--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14670) @PropertyInject : support for complex - non primitive - injection



 [ 
https://issues.apache.org/jira/browse/CAMEL-14670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Luca Burgazzoli updated CAMEL-14670:

Description: 
Camel has a @PropertyInject annotation that works for primitives but it would 
be nice to support complex objects so that one can write:

{code:java}
@BindToRegistry
public static AmazonS3 minioClient(
@PropertyInject("minio") MinioConfig config) {

var endpoint = new 
AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
var credentials = new BasicAWSCredentials(config.getAccessKey(), 
config.getSecretKey());
var credentialsProvider = new AWSStaticCredentialsProvider(credentials);

return AmazonS3ClientBuilder
.standard()
.withEndpointConfiguration(endpoint)
.withCredentials(credentialsProvider)
.withPathStyleAccessEnabled(true)
.build();
}
{code}

And have _minio_ interpreted as properties root so that users can define 
properties like:

{code}
minio.address = http://my-minio.com
minio.access-key = ...
minio.secret-key = ...
{code}

And receive a _MinioConfig_ object configured from those options as method 
parameter.

As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I think 
it would be nice to support such case too.





  was:
Camel has a @PropertyInject annotation that works for primitives but it would 
be nice to support complex objects so that one can write:

{code:java}
@BindToRegistry
public static AmazonS3 minioClient(
@PropertyInject("minio") MinioConfig config) {

var endpoint = new 
AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
var credentials = new BasicAWSCredentials(config.getAccessKey(), 
config.getSecretKey());
var credentialsProvider = new AWSStaticCredentialsProvider(credentials);

return AmazonS3ClientBuilder
.standard()
.withEndpointConfiguration(endpoint)
.withCredentials(credentialsProvider)
.withPathStyleAccessEnabled(true)
.build();
}
{code}

And have _minio_ interpreted as properties root so that users can define 
properties like:

{code}
minio.address = http://my-minio.com
minio.access-key = ...
minio.secret-key = ...
{code}

And receive an _MinioConfig_ object configured from those options as method 
parameter.

As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I think 
it would be nice to support such case too.






> @PropertyInject : support for complex - non primitive - injection
> -
>
> Key: CAMEL-14670
> URL: https://issues.apache.org/jira/browse/CAMEL-14670
> Project: Camel
>  Issue Type: New Feature
>  Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.2.0
>
>
> Camel has a @PropertyInject annotation that works for primitives but it would 
> be nice to support complex objects so that one can write:
> {code:java}
> @BindToRegistry
> public static AmazonS3 minioClient(
> @PropertyInject("minio") MinioConfig config) {
> var endpoint = new 
> AwsClientBuilder.EndpointConfiguration(config.getAddress(), "US_EAST_1");
> var credentials = new BasicAWSCredentials(config.getAccessKey(), 
> config.getSecretKey());
> var credentialsProvider = new AWSStaticCredentialsProvider(credentials);
> return AmazonS3ClientBuilder
> .standard()
> .withEndpointConfiguration(endpoint)
> .withCredentials(credentialsProvider)
> .withPathStyleAccessEnabled(true)
> .build();
> }
> {code}
> And have _minio_ interpreted as properties root so that users can define 
> properties like:
> {code}
> minio.address = http://my-minio.com
> minio.access-key = ...
> minio.secret-key = ...
> {code}
> And receive a _MinioConfig_ object configured from those options as method 
> parameter.
> As today it is possible to achieve a similar behaviour using _@BeanInject_ in 
> combination with https://issues.apache.org/jira/browse/CAMEL-14525 but I 
> think it would be nice to support such case too.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14175) Getting Started guide should be more informative and concise

2020-03-06 Thread Praveen Kottarathil (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053414#comment-17053414
 ] 

Praveen Kottarathil commented on CAMEL-14175:
-

Hi [~smile_outreachy]
 Thank you for offering help with this task. There is a [thread on the dev 
mailing 
list|http://mail-archives.apache.org/mod_mbox/camel-dev/202002.mbox/%3cCAJ1+MEOBTq0dh_WwLCyVGq-sz9hVvUECVa_BWX_xK9=o2mu...@mail.gmail.com%3e],
 where some of the project committers indicated their views and expectations on 
this task (6 Messages so far). You may use it as a high-level guideline.[ This 
commit|https://github.com/PickledDragon/camel/commit/aa6227c0c5349457539a676a496d3b984be42649#diff-3e5fe0caeef794a78d51f0d755c296db]
 is my first attempt at rewriting the `getting started guide`.

> 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] [Created] (CAMEL-14669) Upgrade mockito to 3.3.x

Claus Ibsen created CAMEL-14669:
---

 Summary: Upgrade mockito to 3.3.x
 Key: CAMEL-14669
 URL: https://issues.apache.org/jira/browse/CAMEL-14669
 Project: Camel
  Issue Type: Task
Reporter: Claus Ibsen
 Fix For: 3.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14668) camel-core - Optimize getEndpoint on camel context

Claus Ibsen created CAMEL-14668:
---

 Summary: camel-core - Optimize getEndpoint on camel context
 Key: CAMEL-14668
 URL: https://issues.apache.org/jira/browse/CAMEL-14668
 Project: Camel
  Issue Type: Improvement
Reporter: Claus Ibsen
Assignee: Claus Ibsen
 Fix For: 3.2.0


We can optimize this a bit, and also remove the weird support for endpoints 
without context-paths.

And we can avoid some double encoding if the uri can be fast parsed.



--
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=17053343#comment-17053343
 ] 

Zoran Regvart commented on CAMEL-14175:
---

[~smile_outreachy], [~praveenkottarat...@gmail.com] is already working on this, 
see the comment preceding yours. You can certainly help with this by 
collaborating, reviewing and commenting on the proposed changes made on the 
branch mentioned.

> 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-14667) Searched result div should be scrollable



[ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053342#comment-17053342
 ] 

Zoran Regvart commented on CAMEL-14667:
---

Thanks for creating this issue and working on it, we love contributions :)

> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>  Components: website
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-58-25-810.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-58-25-810.png|width=259,height=459!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14667) Searched result div should be scrollable



 [ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-14667:
--
Component/s: website

> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>  Components: website
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-58-25-810.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-58-25-810.png|width=259,height=459!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14666) Search results push the website's Navbar



 [ 
https://issues.apache.org/jira/browse/CAMEL-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart updated CAMEL-14666:
--
Component/s: website

> Search results push the website's Navbar
> 
>
> Key: CAMEL-14666
> URL: https://issues.apache.org/jira/browse/CAMEL-14666
> Project: Camel
>  Issue Type: Bug
>  Components: website
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-35-11-524.png
>
>
> To produce the bug follow these steps:
> > Go to [https://camel.apache.org/]
> > Try to search for anything.
> > The search result will push the navbar to left.
> Screenshot:
> !image-2020-03-06-15-35-11-524.png|width=571,height=263!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14666) Search results push the website's Navbar



[ 
https://issues.apache.org/jira/browse/CAMEL-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053340#comment-17053340
 ] 

Zoran Regvart commented on CAMEL-14666:
---

Thank you for reporting the issue and working on the fix [~AghaSaad04]!

> Search results push the website's Navbar
> 
>
> Key: CAMEL-14666
> URL: https://issues.apache.org/jira/browse/CAMEL-14666
> Project: Camel
>  Issue Type: Bug
>  Components: website
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-35-11-524.png
>
>
> To produce the bug follow these steps:
> > Go to [https://camel.apache.org/]
> > Try to search for anything.
> > The search result will push the navbar to left.
> Screenshot:
> !image-2020-03-06-15-35-11-524.png|width=571,height=263!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13888) New web site: open foreign links in new window (tab)

2020-03-06 Thread Ifeanyichukwu Nwabuokei (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053314#comment-17053314
 ] 

Ifeanyichukwu Nwabuokei commented on CAMEL-13888:
-

Hello [~zregvart]  I am an Outreachy applicant, I would like to work on this 
task.

> New web site: open foreign links in new window (tab)
> 
>
> Key: CAMEL-13888
> URL: https://issues.apache.org/jira/browse/CAMEL-13888
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Dmitry Volodin
>Priority: Minor
>  Labels: help-wanted
>
> It can be discussing, but would be nice to open all foreign links as new 
> windows (tabs) for better usability while working with site, as some foreign 
> resources not working correctly with return back to the original site page.
> Thank you.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (CAMEL-14666) Search results push the website's Navbar



[ 
https://issues.apache.org/jira/browse/CAMEL-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053288#comment-17053288
 ] 

Agha Saad Fraz edited comment on CAMEL-14666 at 3/6/20, 11:12 AM:
--

The issue is related to the search results as I have mentioned. The possible 
solution would be to add z-index and position properties. I am working on it :) 


was (Author: aghasaad04):
I think the issue is related to the search results as I have mentioned. I think 
the possible solution would be to add z-index and position properties. I am 
working on it :) 

> Search results push the website's Navbar
> 
>
> Key: CAMEL-14666
> URL: https://issues.apache.org/jira/browse/CAMEL-14666
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-35-11-524.png
>
>
> To produce the bug follow these steps:
> > Go to [https://camel.apache.org/]
> > Try to search for anything.
> > The search result will push the navbar to left.
> Screenshot:
> !image-2020-03-06-15-35-11-524.png|width=571,height=263!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14667) Searched result div should be scrollable



 [ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Agha Saad Fraz updated CAMEL-14667:
---
Attachment: image-2020-03-06-15-58-25-810.png

> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-58-25-810.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-47-45-950.png|width=254,height=451!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14667) Searched result div should be scrollable



 [ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Agha Saad Fraz updated CAMEL-14667:
---
Description: 
Steps to produce the issue:

> Type anything in the search field.
 > The resultant div will have search results. But It is not scrollable and the 
 > user will not be able to see all the results.

Screenshot:

!image-2020-03-06-15-58-25-810.png|width=259,height=459!

Possible Solution:

> To add height and overflow-y properties to the resultant div will fix the 
> issue. 

Other possible and efficient solutions are welcome :)

  was:
Steps to produce the issue:

> Type anything in the search field.
 > The resultant div will have search results. But It is not scrollable and the 
 > user will not be able to see all the results.

Screenshot:

!image-2020-03-06-15-47-45-950.png|width=254,height=451!

Possible Solution:

> To add height and overflow-y properties to the resultant div will fix the 
> issue. 

Other possible and efficient solutions are welcome :)


> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-58-25-810.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-58-25-810.png|width=259,height=459!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14667) Searched result div should be scrollable



 [ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Agha Saad Fraz updated CAMEL-14667:
---
Attachment: (was: image-2020-03-06-15-47-45-950.png)

> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-58-25-810.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-47-45-950.png|width=254,height=451!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14667) Searched result div should be scrollable



[ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053302#comment-17053302
 ] 

Agha Saad Fraz commented on CAMEL-14667:


So the possible solution for the above issue is adding the fixed height and 
scrollbar to the resultant div.
Reviews are welcome :)
P.S: I am working on this.

> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-47-45-950.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-47-45-950.png|width=254,height=451!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14667) Searched result div should be scrollable



 [ 
https://issues.apache.org/jira/browse/CAMEL-14667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Agha Saad Fraz updated CAMEL-14667:
---
Description: 
Steps to produce the issue:

> Type anything in the search field.
 > The resultant div will have search results. But It is not scrollable and the 
 > user will not be able to see all the results.

Screenshot:

!image-2020-03-06-15-47-45-950.png|width=254,height=451!

Possible Solution:

> To add height and overflow-y properties to the resultant div will fix the 
> issue. 

Other possible and efficient solutions are welcome :)

  was:
Steps to produce the issue:

> Type anything in the search field.
> The resultant div will have search results. But It is not scrollable and the 
> user will not be able to see all the results.

Screenshot:

!image-2020-03-06-15-47-45-950.png|width=254,height=451!

Possible Solution:

> To add an overflow-y: scroll property to the resultant div.

Other possible and efficient solutions are welcome :)


> Searched result div should be scrollable
> 
>
> Key: CAMEL-14667
> URL: https://issues.apache.org/jira/browse/CAMEL-14667
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-47-36-422.png, 
> image-2020-03-06-15-47-45-950.png
>
>
> Steps to produce the issue:
> > Type anything in the search field.
>  > The resultant div will have search results. But It is not scrollable and 
> the user will not be able to see all the results.
> Screenshot:
> !image-2020-03-06-15-47-45-950.png|width=254,height=451!
> Possible Solution:
> > To add height and overflow-y properties to the resultant div will fix the 
> > issue. 
> Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14667) Searched result div should be scrollable

Agha Saad Fraz created CAMEL-14667:
--

 Summary: Searched result div should be scrollable
 Key: CAMEL-14667
 URL: https://issues.apache.org/jira/browse/CAMEL-14667
 Project: Camel
  Issue Type: Bug
Reporter: Agha Saad Fraz
 Attachments: image-2020-03-06-15-47-36-422.png, 
image-2020-03-06-15-47-45-950.png

Steps to produce the issue:

> Type anything in the search field.
> The resultant div will have search results. But It is not scrollable and the 
> user will not be able to see all the results.

Screenshot:

!image-2020-03-06-15-47-45-950.png|width=254,height=451!

Possible Solution:

> To add an overflow-y: scroll property to the resultant div.

Other possible and efficient solutions are welcome :)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14666) Search results push the website's Navbar



[ 
https://issues.apache.org/jira/browse/CAMEL-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053288#comment-17053288
 ] 

Agha Saad Fraz commented on CAMEL-14666:


I think the issue is related to the search results as I have mentioned. I think 
the possible solution would be to add z-index and position properties. I am 
working on it :) 

> Search results push the website's Navbar
> 
>
> Key: CAMEL-14666
> URL: https://issues.apache.org/jira/browse/CAMEL-14666
> Project: Camel
>  Issue Type: Bug
>Reporter: Agha Saad Fraz
>Priority: Minor
> Attachments: image-2020-03-06-15-35-11-524.png
>
>
> To produce the bug follow these steps:
> > Go to [https://camel.apache.org/]
> > Try to search for anything.
> > The search result will push the navbar to left.
> Screenshot:
> !image-2020-03-06-15-35-11-524.png|width=571,height=263!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14666) Search results push the website's Navbar

Agha Saad Fraz created CAMEL-14666:
--

 Summary: Search results push the website's Navbar
 Key: CAMEL-14666
 URL: https://issues.apache.org/jira/browse/CAMEL-14666
 Project: Camel
  Issue Type: Bug
Reporter: Agha Saad Fraz
 Attachments: image-2020-03-06-15-35-11-524.png

To produce the bug follow these steps:


> Go to [https://camel.apache.org/]
> Try to search for anything.
> The search result will push the navbar to left.

Screenshot:
!image-2020-03-06-15-35-11-524.png|width=571,height=263!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14665) Camel-AWS2 S3: Add downloadLink operation

Andrea Cosentino created CAMEL-14665:


 Summary: Camel-AWS2 S3: Add downloadLink operation
 Key: CAMEL-14665
 URL: https://issues.apache.org/jira/browse/CAMEL-14665
 Project: Camel
  Issue Type: Task
  Components: camel-aws2
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 3.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-14664) Camel-AWS2-S3: add more integration tests



 [ 
https://issues.apache.org/jira/browse/CAMEL-14664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-14664:
-
Summary: Camel-AWS2-S3: add more integration tests  (was: Camel-AWS-S3: add 
more integration tests)

> Camel-AWS2-S3: add more integration tests
> -
>
> Key: CAMEL-14664
> URL: https://issues.apache.org/jira/browse/CAMEL-14664
> Project: Camel
>  Issue Type: Task
>  Components: camel-aws2
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.2.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14663) Camel-AWS2 S3: Add support for multipart download

Andrea Cosentino created CAMEL-14663:


 Summary: Camel-AWS2 S3: Add support for multipart download
 Key: CAMEL-14663
 URL: https://issues.apache.org/jira/browse/CAMEL-14663
 Project: Camel
  Issue Type: Task
  Components: camel-aws2
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 3.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (CAMEL-14643) Configuring brokerurl leads to duplication in camel-activemq and spring-boot



 [ 
https://issues.apache.org/jira/browse/CAMEL-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-14643.
-
  Assignee: Claus Ibsen
Resolution: Fixed

This has been fixed in Camel 3.2 so the default is now true, so when you 
upgrade to this release you can remove that option

> Configuring brokerurl leads to duplication in camel-activemq and spring-boot 
> -
>
> Key: CAMEL-14643
> URL: https://issues.apache.org/jira/browse/CAMEL-14643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq, camel-spring-boot
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Preben Asmussen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.2.0
>
>
> When upgrading from camel 3.0.0 to 3.x.x the spring.activemq.broker-url is no 
> longer used when configuring the camel-activemq component. 
> It seems that you now have to specify both the spring property (for the SB 
> health check to work) and the camel.componnt.activemq.broker-u-r-l for the 
> component to work when picking up configuration properties.
> There is an example here [https://github.com/pax95/failover-test] 
> when you omit the camel.component.activemq.broker-u-r-l the component picks 
> up the default localhost broker and not the spring boot one specified by 
> spring.activemq.broker-url
> Maybe there there are some SB bean conditionals missing ?  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (CAMEL-14664) Camel-AWS-S3: add more integration tests

Andrea Cosentino created CAMEL-14664:


 Summary: Camel-AWS-S3: add more integration tests
 Key: CAMEL-14664
 URL: https://issues.apache.org/jira/browse/CAMEL-14664
 Project: Camel
  Issue Type: Task
  Components: camel-aws2
Reporter: Andrea Cosentino
Assignee: Andrea Cosentino
 Fix For: 3.2.0






--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (CAMEL-14643) Configuring brokerurl leads to duplication in camel-activemq and spring-boot



[ 
https://issues.apache.org/jira/browse/CAMEL-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053257#comment-17053257
 ] 

Claus Ibsen edited comment on CAMEL-14643 at 3/6/20, 10:29 AM:
---

You need to turn on allow to use autowired CF as its mistakenly disabled on SB

 

camel:
 springboot:
 shutdown-timeout: 2
 component:
 activemq:
 allow-auto-wired-connection-factory: true
 health:
 check:
 routes:
 enabled: true


was (Author: davsclaus):
You need to turn on allow to use autowired CF

 

camel:
 springboot:
 shutdown-timeout: 2
 component:
 activemq:
 allow-auto-wired-connection-factory: true
 health:
 check:
 routes:
 enabled: true

> Configuring brokerurl leads to duplication in camel-activemq and spring-boot 
> -
>
> Key: CAMEL-14643
> URL: https://issues.apache.org/jira/browse/CAMEL-14643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq, camel-spring-boot
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Preben Asmussen
>Priority: Major
> Fix For: 3.2.0
>
>
> When upgrading from camel 3.0.0 to 3.x.x the spring.activemq.broker-url is no 
> longer used when configuring the camel-activemq component. 
> It seems that you now have to specify both the spring property (for the SB 
> health check to work) and the camel.componnt.activemq.broker-u-r-l for the 
> component to work when picking up configuration properties.
> There is an example here [https://github.com/pax95/failover-test] 
> when you omit the camel.component.activemq.broker-u-r-l the component picks 
> up the default localhost broker and not the spring boot one specified by 
> spring.activemq.broker-url
> Maybe there there are some SB bean conditionals missing ?  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-14175) Getting Started guide should be more informative and concise

2020-03-06 Thread Muskan (Jira)



[ 
https://issues.apache.org/jira/browse/CAMEL-14175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053260#comment-17053260
 ] 

Muskan commented on CAMEL-14175:


@[~zregvart] Can I work on this task as my first contribution ? 

Do we want the Getting Started Guide to be explaining more about the codebase 
and the installation procedure ?

Thanks

> 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-14643) Configuring brokerurl leads to duplication in camel-activemq and spring-boot



[ 
https://issues.apache.org/jira/browse/CAMEL-14643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053257#comment-17053257
 ] 

Claus Ibsen commented on CAMEL-14643:
-

You need to turn on allow to use autowired CF

 

camel:
 springboot:
 shutdown-timeout: 2
 component:
 activemq:
 allow-auto-wired-connection-factory: true
 health:
 check:
 routes:
 enabled: true

> Configuring brokerurl leads to duplication in camel-activemq and spring-boot 
> -
>
> Key: CAMEL-14643
> URL: https://issues.apache.org/jira/browse/CAMEL-14643
> Project: Camel
>  Issue Type: Bug
>  Components: camel-activemq, camel-spring-boot
>Affects Versions: 3.0.1, 3.1.0
>Reporter: Preben Asmussen
>Priority: Major
> Fix For: 3.2.0
>
>
> When upgrading from camel 3.0.0 to 3.x.x the spring.activemq.broker-url is no 
> longer used when configuring the camel-activemq component. 
> It seems that you now have to specify both the spring property (for the SB 
> health check to work) and the camel.componnt.activemq.broker-u-r-l for the 
> component to work when picking up configuration properties.
> There is an example here [https://github.com/pax95/failover-test] 
> when you omit the camel.component.activemq.broker-u-r-l the component picks 
> up the default localhost broker and not the spring boot one specified by 
> spring.activemq.broker-url
> Maybe there there are some SB bean conditionals missing ?  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CAMEL-13784) Update to AWS SDK V2



 [ 
https://issues.apache.org/jira/browse/CAMEL-13784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino updated CAMEL-13784:
-
Fix Version/s: (was: 3.x)
   3.2.0

> Update to AWS SDK V2
> 
>
> Key: CAMEL-13784
> URL: https://issues.apache.org/jira/browse/CAMEL-13784
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Reporter: Pierre-Yves Bigourdan
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.2.0
>
>
> The [AWS SDK for Java 2.0|https://github.com/aws/aws-sdk-java-v2] reached 
> general availability back in November 2018 (more information on their 
> [official blog 
> post|https://aws.amazon.com/blogs/developer/aws-sdk-for-java-2-x-released]) 
> and has de facto become the preferred way of integrating with AWS using Java.
> Amongst other benefits, using it rather than the old version improves 
> performance and allows to write cleaner code, as it supports more modern 
> language constructs and has a consistent API across the different services.
> The V1 SDK has not yet been officially deprecated, however Camel will need 
> updating at some point, especially as more and more applications are being 
> migrated to use the V2 SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (CAMEL-13784) Update to AWS SDK V2



 [ 
https://issues.apache.org/jira/browse/CAMEL-13784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-13784.
--
Resolution: Fixed

> Update to AWS SDK V2
> 
>
> Key: CAMEL-13784
> URL: https://issues.apache.org/jira/browse/CAMEL-13784
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-aws
>Reporter: Pierre-Yves Bigourdan
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.2.0
>
>
> The [AWS SDK for Java 2.0|https://github.com/aws/aws-sdk-java-v2] reached 
> general availability back in November 2018 (more information on their 
> [official blog 
> post|https://aws.amazon.com/blogs/developer/aws-sdk-for-java-2-x-released]) 
> and has de facto become the preferred way of integrating with AWS using Java.
> Amongst other benefits, using it rather than the old version improves 
> performance and allows to write cleaner code, as it supports more modern 
> language constructs and has a consistent API across the different services.
> The V1 SDK has not yet been officially deprecated, however Camel will need 
> updating at some point, especially as more and more applications are being 
> migrated to use the V2 SDK.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (CAMEL-14555) Create an AWS-S3 component based on SDK v2



 [ 
https://issues.apache.org/jira/browse/CAMEL-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrea Cosentino resolved CAMEL-14555.
--
Resolution: Fixed

> Create an AWS-S3 component based on SDK v2
> --
>
> Key: CAMEL-14555
> URL: https://issues.apache.org/jira/browse/CAMEL-14555
> Project: Camel
>  Issue Type: Sub-task
>  Components: camel-aws
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 3.2.0
>
>




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-11503) Add search

[
https://issues.apache.org/jira/browse/CAMEL-11503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053220#comment-17053220
]

Zoran Regvart commented on CAMEL-11503:
---

Hi [~anna_nidhin] we recently received a contribution, and now the website has
the search functionality, we forgot to resolve this issue.

We much appreciate your interest and willingness to contribute, I don't think
it makes much sense for all of you to work on the same issue. There's also no
need to have a competition on who gets to contribute first, we have plenty of
other issues (outlined below) that you can help with. Since most of you are
interested in participating in the Outreachy program, and help with the
website, please have a look at some issues in that area via this search:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20website

And feel free to propose new ideas by creating new issues around the website.

For those wondering how to get started contributing to the website.

Make sure have a [GitHub account|https://github.com/join], read how you can
[get started|https://help.github.com/en/github/getting-started-with-github],
and [create a pull
request|https://help.github.com/en/github/collaborating-with-issues-and-pull-requests].

Have a look at the
[README.md|https://github.com/apache/camel-website/blob/master/README.md] in
the website project on how to build and how to preview your changes on your own
computer.

I'll try to address the questions in you comments here, for future
conversations please do subscribe to the developer's mailing list and send
emails there, discussions on the Jira issues can get a bit out of control and
it's not that easy to follow the conversation here.

The following text includes information on how to reach us, and get started:

First of all, thank you for having an interest in contributing to Apache Camel.

Here are some guidelines on how to best approach the Apache Camel community and
how to best apply yourself.

1. Communication

Apache Camel is an Apache Software Foundation project, all communication is
done in the open on the project mailing lists.

You can read more on the reasoning behind this to get a better understanding of:

https://www.apache.org/foundation/mailinglists.html

All communication is subject to the ASF Code of Conduct, which you can read
here:

https://www.apache.org/foundation/policies/conduct.html

For questions and guidance around contributing subscribe to the developer's
mailing list by sending an e-mail to dev-subscr...@camel.apache.org.

We can also be reached on the Gitter chat at
https://gitter.im/apache/apache-camel/.

We track issues using ASF Jira located at:

https://issues.apache.org/jira/browse/CAMEL

Where we maintain a list of issues that are easy to get started with, so you
can familiarize yourself with the process and get your first contribution in:

https://issues.apache.org/jira/issues/?filter=12348073

And some areas that we are actively looking for help on:

https://issues.apache.org/jira/issues/?filter=12348074

When you're ready to contribute create a Pull request to one of the Camel
projects you can find under the Apache organization on GitHub:

https://github.com/apache?q=camel

Expect that your Pull request will receive a review and that you will need to
respond and correspond to that via comments at GitHub.

2. Getting started

Read the "Contributing to Apache Camel" document on the Camel website:

https://camel.apache.org/manual/latest/contributing.html

Identify areas you can contribute first. You don't have to be an expert in an
area, the Apache Camel developers are available to offer help and guidance.

Introduce yourself on the developer's mailing list (see above), tell us what
area of work or problem you wish to address in Camel. Create a draft of your
solution, this can be simple 1-2 sentences on the change you wish to make. Try
to be as specific as you can: include a short description of your intent, what
you tried and what didn't work, or what you need help with. The best way of
approaching the developers is by describing what you would like to work on and
asking specific questions on how to get started. We'll do our best to guide you
and help you make your contribution.

We also participate in Google Summer of Code and Outreachy programs, for
information about those look at those program websites. If you wish to
participate in either of those follow the guidelines and schedule set by those
programs. If you're unsure please reach out via official communication channels
of those programs, or ask on the developer's mailing list for help.

3. Your first contribution

Make sure you followed the steps and guidelines outlined above. For bigger
changes, make sure that you have discussed on the developer's mailing list or
in the Jira issue tracker before hand. We

[jira] [Resolved] (CAMEL-11503) Add search



 [ 
https://issues.apache.org/jira/browse/CAMEL-11503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Zoran Regvart resolved CAMEL-11503.
---
Resolution: Implemented

Thanks to [~nayanagamuhandiram] for the contribution!

> Add search
> --
>
> Key: CAMEL-11503
> URL: https://issues.apache.org/jira/browse/CAMEL-11503
> Project: Camel
>  Issue Type: Sub-task
>  Components: website
>Reporter: Zoran Regvart
>Priority: Major
>  Labels: help-wanted
>
> There are a couple of [search|https://gohugo.io/tools/#search] options 
> mentioned on the Hugo website, implement one of those, or use Google (or 
> other search engine) custom site search.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (CAMEL-13564) Split exception/error handling model from runtime

[
https://issues.apache.org/jira/browse/CAMEL-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053217#comment-17053217
]

Zoran Regvart commented on CAMEL-13564:
---

Hi [~Gaelle], for the Outreachy program our project proposal is for the Camel
Website, this is the text I prepared to get started please have a look:

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20website

And feel free to propose new ideas by creating new issues around the website.

For those wondering how to get started contributing to the website.

Have a look at the
[README.md|https://github.com/apache/camel-website/blob/master/README.md] in
the website project on how to build and how to preview your changes on your own
computer.

The following text includes information on how to reach us, and get started:

First of all, thank you for having an interest in contributing to Apache Camel.

Here are some guidelines on how to best approach the Apache Camel community and
how to best apply yourself.

1. Communication

Apache Camel is an Apache Software Foundation project, all communication is
done in the open on the project mailing lists.

You can read more on the reasoning behind this to get a better understanding of:

https://www.apache.org/foundation/mailinglists.html

All communication is subject to the ASF Code of Conduct, which you can read
here:

https://www.apache.org/foundation/policies/conduct.html

For questions and guidance around contributing subscribe to the developer's
mailing list by sending an e-mail to dev-subscr...@camel.apache.org.

We can also be reached on the Gitter chat at
https://gitter.im/apache/apache-camel/.

We track issues using ASF Jira located at:

https://issues.apache.org/jira/browse/CAMEL

Where we maintain a list of issues that are easy to get started with, so you
can familiarize yourself with the process and get your first contribution in:

https://issues.apache.org/jira/issues/?filter=12348073

And some areas that we are actively looking for help on:

https://issues.apache.org/jira/issues/?filter=12348074

When you're ready to contribute create a Pull request to one of the Camel
projects you can find under the Apache organization on GitHub:

https://github.com/apache?q=camel

Expect that your Pull request will receive a review and that you will need to
respond and correspond to that via comments at GitHub.

2. Getting started

Read the "Contributing to Apache Camel" document on the Camel website:

https://camel.apache.org/manual/latest/contributing.html

Identify areas you can contribute first. You don't have to be an expert in an
area, the Apache Camel developers are available to offer help and guidance.

3. Your first contribution

Make sure you followed the steps and guidelines outlined above. For bigger
changes, make sure that you have discussed on the developer's mailing list or
in the Jira issue tracker before

[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=17053213#comment-17053213
]

Zoran Regvart commented on CAMEL-14567:
---

Hi all, just in case you haven't already received this information on how to
contribute I'll enclose it in here first, I'll try to address your individual
comments next.

https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20website

And feel free to propose new ideas by creating new issues around the website.

For those wondering how to get started contributing to the website.

Have a look at the
[README.md|https://github.com/apache/camel-website/blob/master/README.md] in
the website project on how to build and how to preview your changes on your own
computer.

The following text includes information on how to reach us, and get started:

First of all, thank you for having an interest in contributing to Apache Camel.

Here are some guidelines on how to best approach the Apache Camel community and
how to best apply yourself.

1. Communication

Apache Camel is an Apache Software Foundation project, all communication is
done in the open on the project mailing lists.

You can read more on the reasoning behind this to get a better understanding of:

https://www.apache.org/foundation/mailinglists.html

All communication is subject to the ASF Code of Conduct, which you can read
here:

https://www.apache.org/foundation/policies/conduct.html

For questions and guidance around contributing subscribe to the developer's
mailing list by sending an e-mail to dev-subscr...@camel.apache.org.

We can also be reached on the Gitter chat at
https://gitter.im/apache/apache-camel/.

We track issues using ASF Jira located at:

https://issues.apache.org/jira/browse/CAMEL

Where we maintain a list of issues that are easy to get started with, so you
can familiarize yourself with the process and get your first contribution in:

https://issues.apache.org/jira/issues/?filter=12348073

And some areas that we are actively looking for help on:

https://issues.apache.org/jira/issues/?filter=12348074

When you're ready to contribute create a Pull request to one of the Camel
projects you can find under the Apache organization on GitHub:

https://github.com/apache?q=camel

Expect that your Pull request will receive a review and that you will need to
respond and correspond to that via comments at GitHub.

2. Getting started

Read the "Contributing to Apache Camel" document on the Camel website:

https://camel.apache.org/manual/latest/contributing.html

Identify areas you can contribute first. You don't have to be an expert in an
area, the Apache Camel developers are available to offer help and guidance.

3. Your first contribution

Make sure you followed the steps and guidelines outlined above. For bigger
changes, make sure that you have discussed on the developer's mailing list or
in the Jira

[jira] [Commented] (CAMEL-13888) New web site: open foreign links in new window (tab)