Hi
Read the java doc of the API of the producer template etc if you use
that to send to endpoints.
eg if you use the api that returns an exchange then you must check
yourself if its failed or not.
Also you must call done unit of work when you are done with the
exchange etc. But its documented in t
No problem. Glad to help.
Inviato da Yahoo Mail su Android
Il mer, 6 nov, 2019 alle 18:38, Pascal Schumacher
ha scritto: Seem like I am missing the "linking of accounts through
https://gitbox.apache.org/setup/"; step mentioned in
https://blogs.apache.org/infra/entry/apache-and-github-a-fri
Seem like I am missing the "linking of accounts through
https://gitbox.apache.org/setup/"; step mentioned in
https://blogs.apache.org/infra/entry/apache-and-github-a-friendly
Sorry for the noise,
Pascal
Am 06.11.2019 um 18:27 schrieb Andrea Cosentino:
Did you follow the gitbox integration work
No idea what's wrong
Il mer 6 nov 2019, 18:27 Andrea Cosentino ha scritto:
> Did you follow the gitbox integration workflow?
>
> Il mer 6 nov 2019, 18:22 Pascal Schumacher ha
> scritto:
>
>> Yes, the commit are no longer in the gitbox repo.
>>
>> I am pushing to gitbox because when I try to pus
Did you follow the gitbox integration workflow?
Il mer 6 nov 2019, 18:22 Pascal Schumacher ha
scritto:
> Yes, the commit are no longer in the gitbox repo.
>
> I am pushing to gitbox because when I try to push to the camel repo on
> github it tells me that I am not authorized. Even-though I am pa
Yes, the commit are no longer in the gitbox repo.
I am pushing to gitbox because when I try to push to the camel repo on
github it tells me that I am not authorized. Even-though I am part ofÂ
"The Apache Foundation" organization on github. Pushing to other github
repos works fine. Not sure what I
Hello team,
I have a question if we have enough documents to prove what is mentioned in
https://issues.apache.org/jira/browse/CAMEL-14144
Could you please have a look it ?
Thanks & Regards,
Shahbaz Akhter
Hi David,
The ability to map src/main/docs to the Antora expected directory
structure, as you're proposing looks better to me. This would save us
from having to do those "regen" commits when we make a change to the
component documentation and commit without running the build in
`docs/`. Thank you f
