Re: Camel 4 roadmap and affect on Camel 3

2022-11-30 Thread Francois Papon
OSGi metadata in manifest is different than Karaf feature for managing 
bundle dependencies in component integration.


I think that there is no effort from Camel team to keep the 
maven-bundle-plugin from the main source modules.


On 30/11/2022 18:15, Claus Ibsen wrote:

Camel Karaf project generates JARs for what Camel components they support
only - the same is what we do for Spring Boot / Quarkus / Camel Kafka
Connector etc.
JB talks about Karaf 5 with a new way of deploying that sounds like this
can be done smarter and easier.

For example if Camel Karaf support camel-ftp, then they can build and
release

org.apache.karaf.camel:camel-ftp-bundle:4.0.0




On Wed, Nov 30, 2022 at 2:09 PM Siano, Stephan
 wrote:


Hi,

Actually removing the OSGi manifests from the bundles coming from the
general camel build would mean that we have to create an OSGi wrapper
bundle for each and every jar coming out of the general build, which looks
like a lot of maintenance effort to me.

Best regards
Stephan

-Original Message-
From: fpapon 
Sent: Wednesday, 30 November 2022 14:01
To: dev@camel.apache.org
Subject: Re: Camel 4 roadmap and affect on Camel 3

Ok so we will have a camel-core.jar and camel-core-with-manifest-osgi.jar
just with the manifest file add-in for each camel core jar.

On 30/11/2022 13:53, Andrea Cosentino wrote:

This would become something karaf-camel is responsible for.



Il giorno mer 30 nov 2022 alle ore 13:49 fpapon  ha
scritto:


Hi,

For this point "Camel v4 core and component JARs will no longer
generate OSGi MANIFEST.MF" I'm not sure that removing the generation
from the core Camel is a good thing...

regards,

François

On 30/11/2022 10:44, Claus Ibsen wrote:

Hi



On Mon, Nov 28, 2022 at 10:40 AM Jean-Baptiste Onofré

wrote:


Hi guys,

I understand that Karaf/OSGi is not in the Camel community target
anymore, and it makes sense.
I proposed a time ago to refactor the approach of Camel components
for Karaf, using special packaging (embedded the deps as private to
avoid to have bunch of SMX bundles deps), etc.

Even at Karaf, there are discussions about the next step in the
project decoupled from OSGi (see Minho).

I would split the discussion in two parts:
- In terms of the roadmap/Camel future, I don't think it's worth it
for Camel community to maintain OSGi/Karaf support anymore. It's
always possible to wrap Camel routes in an uber jar and deploy in
Karaf.
- In terms of community/maintenance, I think camel-karaf could be
part of the Karaf community. We had a similar discussion about
jclouds: the jclouds community didn't want to maintain
jclouds-karaf anymore (for the same reasons as the Camel
community). The jclouds community asked the karaf community if they
were interested in maintaining and managing jclouds-karaf. So we
can do the same for camel-karaf: the karaf community can take the

lead there and maintain it.

Thoughts ?



Yes i Agree on this JB.

- Move camel-karaf to Apache Karaf as a new karaf-camel sub-project,
and let the community and committers in that project take over
maintaining

and

releasing this.
- For Camel v4 onwards then camel-karaf will no longer be part of
Apache Camel.
- Karaf Camel is released under a new GAV - org.apache.karaf.camel,
and

no

longer org.apache.camel.karaf.
- Camel v4 core and component JARs will no longer generate OSGi

MANIFEST.MF

as Karaf Camel will be responsible for this (if even needed); such
as JB talks about a new way of packing and running things in Karaf.
- For Camel v3 we keep as-is and maintain and release camel-karaf
until Camel 3 is EOL





Regards
JB

On Sat, Nov 26, 2022 at 9:51 AM Andrea Cosentino

wrote:

Hello

I'll come back for other questions. Let me just say that
camel-karaf is

too

hard to maintain today. If it won't be released because of

misalignments,

it should be aligned by some volunteers or community member and

released

later. Active contributors are not really focused on Karaf runtime
and

we

cannot do everything. This doesn't mean we won't release camel
Karaf anymore. It only means it could be released later on. Even
after the

core

camel and SB part have been released.

In more than one situation aligning OSGi stuff have been really hard.

Less

and less community members are helping on the Karaf side and
releasing sometimes have been slow down by these troubles. Also
OSGi have been

drop

in a lot of 3rd party libraries.

So I'm +1 with this approach.

I'll continue the discussion in the next days for the other points.

Cheers


Il ven 25 nov 2022, 15:06 Nicolas Filotto  ha

scritto:

Hi Claus,

That sounds like a good plan, here are the first questions that I
have

in

mind:

 *   Why do we need to keep on releasing new LTS versions of

Camel

3?

 *   Why not simply consider 3.20 as the last LTS version of

Camel 3

and

only maintain it?
 *   What kind of features/improvements do you want to add to

Camel

3

after releasing 3.20?
 *   If camel-karaf is released 

Re: [VOTE] Release Apache Camel 3.15.0

2022-02-01 Thread Francois Papon

+1 (non-binding)

thanks!

regards,

François

On 01/02/2022 07:39, Gregor Zurowski wrote:

Hi Everyone:

This is a vote to release Apache Camel 3.15.0, a new release with 217
new features and improvements.

Release notes: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350874=12311211

== Apache Camel 3.15.0 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1407/

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1407/org/apache/camel/apache-camel/3.15.0/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.15.0

== Apache Camel Spring Boot 3.15.0 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1408/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.15.0

== Apache Camel Karaf 3.15.0 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1409/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.15.0

Please test this release candidate and cast your vote.

[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.15.0
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor


Re: [VOTE] Release Apache Camel 3.14.1

2022-01-26 Thread Francois Papon

+1 (non-binding)

Thanks!

regards,

François

On 24/01/2022 09:56, Gregor Zurowski wrote:

Hi Everyone:

This is a vote to release Apache Camel 3.14.1, a new patch release
with 47 fixes and improvements.

Release notes: 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12351060=12311211

== Apache Camel 3.14.1 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1402/

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1402/org/apache/camel/apache-camel/3.14.1/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.14.1

== Apache Camel Spring Boot 3.14.1 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1403/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.14.1

== Apache Camel Karaf 3.14.1 ==

Staging repository:
https://repository.apache.org/content/repositories/orgapachecamel-1404/

Tag: 
https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.14.1

Please test this release candidate and cast your vote:
[ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
Karaf 3.14.1
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor


Re: Camel load resource from classloader broken

2022-01-03 Thread Francois Papon

Hi JB,

Sure, here the Jira:

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

Thanks for your help!

Regards,

François

On 03/01/2022 18:06, Jean-Baptiste Onofré wrote:

Hi François,

thanks for pointing this.

That's a *huge* regression impacting camel-karaf.
Definitely we have to fix that (I consider this regression as 
blocker/critical).


Can you create a Jira about that, I will fix that ?

Thanks,
Regards
JB

On 03/01/2022 17:35, Francois Papon wrote:

Hi,

It seems like this commit broke the OSGi compatibility by loading 
resources from another classloader:


https://github.com/apache/camel/commit/11bd8012743868712904b449024344bcf8130d2b#diff-8514339d35970f5c1e68df154846a293656b9a482d332b7f4423755ba0d2b0f9 



For example, when upgrading to Camel 3.14.0, we have this error when 
starting a quartz route endpoint:


Caused by: java.lang.RuntimeException: org.quartz.SchedulerException: 
Quartz properties file not found in classpath: 
org/quartz/quartz.properties


Regards,

Francois



Camel load resource from classloader broken

2022-01-03 Thread Francois Papon

Hi,

It seems like this commit broke the OSGi compatibility by loading 
resources from another classloader:


https://github.com/apache/camel/commit/11bd8012743868712904b449024344bcf8130d2b#diff-8514339d35970f5c1e68df154846a293656b9a482d332b7f4423755ba0d2b0f9

For example, when upgrading to Camel 3.14.0, we have this error when 
starting a quartz route endpoint:


Caused by: java.lang.RuntimeException: org.quartz.SchedulerException: 
Quartz properties file not found in classpath: org/quartz/quartz.properties


Regards,

Francois



Re: Karaf/Camel camel-elasticsearch-rest component and Log4jShell

2022-01-03 Thread Francois Papon
I will made some tests on camel-karaf main branch because I made it work 
on a custom Karaf distribution by adding blacklisted bundle.


However I don't install all the features but it's weird because in the 
feature.xml of camel-karaf, only the elasticsearch feature depend on log4j.


On 03/01/2022 16:47, Andrea Cosentino wrote:

If you run a full feature install like we do in camel-karaf it will fail.

This the only test i've done around ES feature

Il lun 3 gen 2022, 16:46 Francois Papon  ha
scritto:


The range of the import package is
org.apache.logging.log4j;version="[2.8,4)" in the servicemix bundle so
it should work if we only upgrade log4j version no?

May be I missed somethings.

On 03/01/2022 16:33, Andrea Cosentino wrote:

No, the installation will fail if you update the feature without

upgrading

elasticsearch bundle.

We cannot update the ES bundle for the license problem.

Il giorno lun 3 gen 2022 alle ore 16:31 Francois Papon <
francois.pa...@openobject.fr> ha scritto:


Ok, so just updating the feature should be enought.

On 03/01/2022 16:29, Andrea Cosentino wrote:

Elasticsearch high level client and all the related stuff changed their
license after 7.10.2

As far as I know is not compatible with ASF License.

This is the reason is not updated.

Il giorno lun 3 gen 2022 alle ore 16:27 Francois Papon <
francois.pa...@openobject.fr> ha scritto:


Hi,

The Camel elasticsearch-rest-component depend on the version 7.10.2 of
elasticsearch-client that has a dependency on log4j-core:2.13.3 and
log4j-api:2.13.3

When installating the Karaf feature the log4j bundles are installed:




https://github.com/apache/camel-karaf/blob/e976acc7c1d6405b283ffe3e69d336aab854bd5b/pom.xml#L232

There is a comment about upgrading but with a warning about other
features compatibility.

Does anyone has some information about this?

Do we need to upgrade?

The Elasticsearch team upgraded to log4j:2.17.0 on 7.16.2.

May be Servicemix bundle should be update too.

Regards,

Francois






Re: Karaf/Camel camel-elasticsearch-rest component and Log4jShell

2022-01-03 Thread Francois Papon
The range of the import package is 
org.apache.logging.log4j;version="[2.8,4)" in the servicemix bundle so 
it should work if we only upgrade log4j version no?


May be I missed somethings.

On 03/01/2022 16:33, Andrea Cosentino wrote:

No, the installation will fail if you update the feature without upgrading
elasticsearch bundle.

We cannot update the ES bundle for the license problem.

Il giorno lun 3 gen 2022 alle ore 16:31 Francois Papon <
francois.pa...@openobject.fr> ha scritto:


Ok, so just updating the feature should be enought.

On 03/01/2022 16:29, Andrea Cosentino wrote:

Elasticsearch high level client and all the related stuff changed their
license after 7.10.2

As far as I know is not compatible with ASF License.

This is the reason is not updated.

Il giorno lun 3 gen 2022 alle ore 16:27 Francois Papon <
francois.pa...@openobject.fr> ha scritto:


Hi,

The Camel elasticsearch-rest-component depend on the version 7.10.2 of
elasticsearch-client that has a dependency on log4j-core:2.13.3 and
log4j-api:2.13.3

When installating the Karaf feature the log4j bundles are installed:




https://github.com/apache/camel-karaf/blob/e976acc7c1d6405b283ffe3e69d336aab854bd5b/pom.xml#L232

There is a comment about upgrading but with a warning about other
features compatibility.

Does anyone has some information about this?

Do we need to upgrade?

The Elasticsearch team upgraded to log4j:2.17.0 on 7.16.2.

May be Servicemix bundle should be update too.

Regards,

Francois






Re: Karaf/Camel camel-elasticsearch-rest component and Log4jShell

2022-01-03 Thread Francois Papon

Ok, so just updating the feature should be enought.

On 03/01/2022 16:29, Andrea Cosentino wrote:

Elasticsearch high level client and all the related stuff changed their
license after 7.10.2

As far as I know is not compatible with ASF License.

This is the reason is not updated.

Il giorno lun 3 gen 2022 alle ore 16:27 Francois Papon <
francois.pa...@openobject.fr> ha scritto:


Hi,

The Camel elasticsearch-rest-component depend on the version 7.10.2 of
elasticsearch-client that has a dependency on log4j-core:2.13.3 and
log4j-api:2.13.3

When installating the Karaf feature the log4j bundles are installed:


https://github.com/apache/camel-karaf/blob/e976acc7c1d6405b283ffe3e69d336aab854bd5b/pom.xml#L232

There is a comment about upgrading but with a warning about other
features compatibility.

Does anyone has some information about this?

Do we need to upgrade?

The Elasticsearch team upgraded to log4j:2.17.0 on 7.16.2.

May be Servicemix bundle should be update too.

Regards,

Francois






Karaf/Camel camel-elasticsearch-rest component and Log4jShell

2022-01-03 Thread Francois Papon

Hi,

The Camel elasticsearch-rest-component depend on the version 7.10.2 of 
elasticsearch-client that has a dependency on log4j-core:2.13.3 and 
log4j-api:2.13.3


When installating the Karaf feature the log4j bundles are installed:

https://github.com/apache/camel-karaf/blob/e976acc7c1d6405b283ffe3e69d336aab854bd5b/pom.xml#L232

There is a comment about upgrading but with a warning about other 
features compatibility.


Does anyone has some information about this?

Do we need to upgrade?

The Elasticsearch team upgraded to log4j:2.17.0 on 7.16.2.

May be Servicemix bundle should be update too.

Regards,

Francois





Re: [VOTE] Release Apache Camel 3.11.2 (LTS)

2021-09-10 Thread Francois Papon
+1 (non-binding)

thanks for the release!

regards,

François
fpa...@apache.org
francois.pa...@openobject.fr

Le 10/09/2021 à 12:11, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.11.2, a new patch release for
> Camel 3.11 with 28 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350487=12311211
>
> == Apache Camel 3.11.2 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1353/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1353/org/apache/camel/apache-camel/3.11.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.11.2
>
> == Apache Camel Spring Boot 3.11.2 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1355/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.11.2
>
> == Apache Camel Karaf 3.11.2 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1356/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.11.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.11.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: Camel 3.11.2 patch release

2021-09-09 Thread Francois Papon
Thanks a lot guys!

regards,

François
fpa...@apache.org
francois.pa...@openobject.fr

Le 09/09/2021 à 11:30, Gregor Zurowski a écrit :
> Yes, I can cherry-pick this onto the 3.11.x branch once the PR is
> merged into main.
>
> Thanks,
> Gregor
>
> On Thu, Sep 9, 2021 at 11:19 AM Francois Papon
>  wrote:
>> Hi,
>>
>> Is it possible to include this PR from camel-karaf repo in the release?
>>
>> https://github.com/apache/camel-karaf/pull/83
>>
>> It's a blocker about karaf custom distribution builder.
>>
>> regards,
>>
>> François
>> fpa...@apache.org
>> francois.pa...@openobject.fr
>>
>> Le 09/09/2021 à 11:14, Jean-Baptiste Onofre a écrit :
>>> Hi Gregor,
>>>
>>> Yes, I confirm that the issue is fixed on main and 3.11.x branches.
>>>
>>> It’s ok for the release.
>>>
>>> Thanks !
>>>
>>> Regards
>>> JB
>>>
>>>> Le 9 sept. 2021 à 11:10, Gregor Zurowski  a 
>>>> écrit :
>>>>
>>>> Hey JB,
>>>>
>>>> Were you able to verify that everything's working with Karaf?
>>>>
>>>> Thanks,
>>>> Gregor
>>>>
>>>> On Thu, Sep 9, 2021 at 10:27 AM Jean-Baptiste Onofre  
>>>> wrote:
>>>>> I’m checking to see if it’s OK with OSGi/Karaf as well.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>> Le 9 sept. 2021 à 10:26, Claus Ibsen  a écrit :
>>>>>>
>>>>>> Its already been fixed, as quarkus also reported this dual package 
>>>>>> "problem".
>>>>>> https://github.com/apache/camel/commit/6c3b40bac491b6a7704501d2ddeacbc854552113
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 9, 2021 at 10:13 AM Jean-Baptiste Onofre  
>>>>>> wrote:
>>>>>>> Checking now, I will keep you posted asap.
>>>>>>>
>>>>>>> Thanks !
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>> Le 9 sept. 2021 à 10:12, Gregor Zurowski  a 
>>>>>>>> écrit :
>>>>>>>>
>>>>>>>> It's not a problem to restart the release. When do you expect to 
>>>>>>>> commit the fix?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Gregor
>>>>>>>>
>>>>>>>> On Thu, Sep 9, 2021 at 10:08 AM Jean-Baptiste Onofre 
>>>>>>>>  wrote:
>>>>>>>>> I just created: https://issues.apache.org/jira/browse/CAMEL-16935
>>>>>>>>>
>>>>>>>>> Due to the commit mentioned in my previous email, both camel-main and 
>>>>>>>>> camel-base-engine bundles export org.apache.camel.main package, which 
>>>>>>>>> is wrong.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>>> Le 9 sept. 2021 à 10:07, Andrea Cosentino 
>>>>>>>>>>  a écrit :
>>>>>>>>>>
>>>>>>>>>> What is the issue?
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Andrea Cosentino
>>>>>>>>>> --
>>>>>>>>>> Apache Camel PMC Chair
>>>>>>>>>> Apache Karaf Committer
>>>>>>>>>> Apache Servicemix PMC Member
>>>>>>>>>> Email: ancosen1...@yahoo.com
>>>>>>>>>> Twitter: @oscerd2
>>>>>>>>>> Github: oscerd
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Thursday, September 9, 2021, 10:03:43 AM GMT+2, Jean-Baptiste 
>>>>>>>>>> Onofre  wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>&g

Re: Camel 3.11.2 patch release

2021-09-09 Thread Francois Papon
Hi,

Is it possible to include this PR from camel-karaf repo in the release?

https://github.com/apache/camel-karaf/pull/83

It's a blocker about karaf custom distribution builder.

regards,

François
fpa...@apache.org
francois.pa...@openobject.fr

Le 09/09/2021 à 11:14, Jean-Baptiste Onofre a écrit :
> Hi Gregor,
>
> Yes, I confirm that the issue is fixed on main and 3.11.x branches.
>
> It’s ok for the release.
>
> Thanks !
>
> Regards
> JB
>
>> Le 9 sept. 2021 à 11:10, Gregor Zurowski  a écrit :
>>
>> Hey JB,
>>
>> Were you able to verify that everything's working with Karaf?
>>
>> Thanks,
>> Gregor
>>
>> On Thu, Sep 9, 2021 at 10:27 AM Jean-Baptiste Onofre  
>> wrote:
>>> I’m checking to see if it’s OK with OSGi/Karaf as well.
>>>
>>> Regards
>>> JB
>>>
 Le 9 sept. 2021 à 10:26, Claus Ibsen  a écrit :

 Its already been fixed, as quarkus also reported this dual package 
 "problem".
 https://github.com/apache/camel/commit/6c3b40bac491b6a7704501d2ddeacbc854552113


 On Thu, Sep 9, 2021 at 10:13 AM Jean-Baptiste Onofre  
 wrote:
> Checking now, I will keep you posted asap.
>
> Thanks !
>
> Regards
> JB
>
>> Le 9 sept. 2021 à 10:12, Gregor Zurowski  a 
>> écrit :
>>
>> It's not a problem to restart the release. When do you expect to commit 
>> the fix?
>>
>> Thanks,
>> Gregor
>>
>> On Thu, Sep 9, 2021 at 10:08 AM Jean-Baptiste Onofre  
>> wrote:
>>> I just created: https://issues.apache.org/jira/browse/CAMEL-16935
>>>
>>> Due to the commit mentioned in my previous email, both camel-main and 
>>> camel-base-engine bundles export org.apache.camel.main package, which 
>>> is wrong.
>>>
>>> Regards
>>> JB
>>>
 Le 9 sept. 2021 à 10:07, Andrea Cosentino 
  a écrit :

 What is the issue?

 --
 Andrea Cosentino
 --
 Apache Camel PMC Chair
 Apache Karaf Committer
 Apache Servicemix PMC Member
 Email: ancosen1...@yahoo.com
 Twitter: @oscerd2
 Github: oscerd






 On Thursday, September 9, 2021, 10:03:43 AM GMT+2, Jean-Baptiste 
 Onofre  wrote:





 Hi,

 I detected an issue about camel-main introduced by the following 
 commit:

 https://github.com/apache/camel/commit/a010b1486bb0668708cc2b04ddf12c9cb6e835a3#diff-07a341b074a4f0b518090873308d53d3e2cbf08ba1cb94bc83be8516c412eea7

 Can I still have time to include in 3.11.2 ? Or should I fix for 
 3.11.3 ?

 Regards
 JB

> Le 9 sept. 2021 à 10:00, Gregor Zurowski  a 
> écrit :
>
> I verified the 3.11.x branch yesterday and started to cut the release
> this morning. Will post updates.
>
> Thanks,
> Gregor
>
> On Thu, Sep 9, 2021 at 9:00 AM Claus Ibsen  
> wrote:
>> Hi Gregor
>>
>> You are welcome to start cutting the release.
>>
>> On Mon, Sep 6, 2021 at 2:26 PM Gregor Zurowski 
>>  wrote:
>>> I'd be available to cut the release candidate this Wednesday.
>>>
>>> Gregor
>>>
>>> On Fri, Sep 3, 2021, 3:12 PM Claus Ibsen  
>>> wrote:
>>>
 Hi

 Okay have upgraded to SB 2.5.4

 On Fri, Sep 3, 2021 at 12:18 PM Claus Ibsen 
  wrote:
> Hi
>
> I think we should start preparing for cutting a new patch release.
>
> There is a task to upgrade to spring boot 2.5.4 that should be 
> done
 first.
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2


 --
 Claus Ibsen
 -
 http://davsclaus.com @davsclaus
 Camel in Action 2: https://www.manning.com/ibsen2

>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2

 --
 Claus Ibsen
 -
 http://davsclaus.com @davsclaus
 Camel in Action 2: https://www.manning.com/ibsen2


Re: [VOTE] Release Apache Camel 3.7.4 with Spring Boot and Karaf Support Projects

2021-04-30 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 29/04/2021 à 19:31, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.7.4 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 19 improvements
> and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349972=12311220
>
> == Apache Camel 3.7.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1313/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1313/org/apache/camel/apache-camel/3.7.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.7.4
>
> == Apache Camel Spring Boot 3.7.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1314/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.7.4
>
> == Apache Camel Karaf 3.7.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1315/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.7.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.7.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.8.0 with Spring Boot and Karaf Support Projects

2021-02-10 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 10/02/2021 à 08:52, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.8.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 160
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349420=12311220
>
> == Apache Camel 3.8.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1286/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1286/org/apache/camel/apache-camel/3.8.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.8.0
>
> == Apache Camel Spring Boot 3.8.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1287/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.8.0
>
> == Apache Camel Karaf 3.8.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1288/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.8.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.8.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.7.0 with Spring Boot and Karaf Support Projects

2020-12-13 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 13/12/2020 à 09:15, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.7.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 185
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349250=12311220
>
> == Apache Camel 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1263/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1263/org/apache/camel/apache-camel/3.7.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.7.0
>
> == Apache Camel Spring Boot 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1264/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.7.0
>
> == Apache Camel Karaf 3.7.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1265/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.7.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.7.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.4.4 (LTS)

2020-09-24 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 23/09/2020 à 15:35, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.4.4, a new patch release for
> the 3.4.x LTS branch with 31 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348674=12311211
>
> == Apache Camel 3.4.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1248/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1248/org/apache/camel/apache-camel/3.4.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.4
>
> == Apache Camel Spring Boot 3.4.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1249/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.4
>
> == Apache Camel Karaf 3.4.4 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1250/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.4.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.5.0 with Spring Boot and Karaf Support Projects

2020-09-02 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 01/09/2020 à 16:59, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.5.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 240
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348299=12311220
>
> == Apache Camel 3.5.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1243/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1243/org/apache/camel/apache-camel/3.5.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.5.0
>
> == Apache Camel Spring Boot 3.5.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1244/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.5.0
>
> == Apache Camel Karaf 3.5.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1245/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.5.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.5.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel Quarkus 1.0.1

2020-08-27 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 26/08/2020 à 22:05, Peter Palaga a écrit :
> Hi,
>
> This is a vote to release Apache Camel Quarkus 1.0.1 - the first patch
> release in the new 1.0.x branch.
>
> Highlights:
> * Camel 3.4.3
> * Quarkus 1.7.1.Final
> * All changes since 1.0.0 (all backported from the master)
> https://github.com/apache/camel-quarkus/compare/1.0.0...1.0.1
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1242
>
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=commit;h=c324819b5aa0071f3c4ee942949b46eefcf3e2eb
>
>
> Source release package:
> https://repository.apache.org/service/local/repositories/orgapachecamel-1242/content/org/apache/camel/quarkus/camel-quarkus/1.0.1/camel-quarkus-1.0.1-src.zip
>
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel Quarkus 1.0.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Many thanks to all contributors!
>
> -- Peter
>


Re: Alternatives to gitter

2020-08-20 Thread Francois Papon
Hi,

Why not using the ASF Slack workspace?

There is an existing Camel channel.

regards,

François
fpa...@apache.org

Le 20/08/2020 à 13:12, Luca Burgazzoli a écrit :
> Hello,
>
> Over the past months I've been trying to be more active on gitter on the
> various camel projects and  overall the user experience was quite terrible
> for me (in particular when using the mobile client), as example:
>
> - threads are not shown properly on the iOS client thus messages are
> messing up
> - messages are extremely slow to load and sometime the message you sent
> take quite long to be visible even on your end so you don't actually know
> what it is happening
> - messages keep being marked as unread even if you did read them
> - sometimes you need to close/reopen the thread sidebar to see new messages
> for a given thread
>
> I don't know if it is only me but because of my frustration with the tool
> I'd like to know if anyone is interested in evaluating some alternatives
> (please note that we DON'T necessarily need to switch to something
> different).
>
> I'd personally would like to suggest to try out Zulip (
> https://zulipchat.com/) as it allow us to have an independent organization (
> camel.zulipchat.com) and to login with github/gitter/google so you can
> easily join without having to fill gazillion of details but I know it's
> streams and topic way of organizing conversations may not be optimal for
> everyone.
>
> If anyone has suggestions, let discuss here.
>
>
> ---
> Luca Burgazzoli
>


Re: [VOTE] Release Apache Camel 3.4.3 (LTS)

2020-08-12 Thread Francois Papon
+1 (non-binding)

Thanks for the release!

regards,

François
fpa...@apache.org

Le 12/08/2020 à 09:55, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.4.3, a new patch release for
> the 3.4.x LTS branch with 33 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348603=12311211
>
> == Apache Camel 3.4.3 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1239/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1239/org/apache/camel/apache-camel/3.4.3/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.3
>
> == Apache Camel Spring Boot 3.4.3 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1240/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.3
>
> == Apache Camel Karaf 3.4.3 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1241/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.3
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.4.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [HEADS UP/PROPOSAL] "New" Camel Karaf for 3.5.0

2020-06-23 Thread Francois Papon
Hi JB,

I think it make a lot of senses, especially to help users to build a
custom Karaf/Camel distribution!

regards,

François
fpa...@apache.org

Le 22/06/2020 à 19:09, Jean-Baptiste Onofre a écrit :
> Hi guys,
>
> Now that Camel Karaf is on its own repository, I started major 
> refactoring/improvement coming for 3.5.0 (as 3.4.0 is LTS):
>
> 1. Cleanup
> I did a complete module structure cleanup (no platform anymore, core module 
> directly at root folder) and feature.
>
> 2. Remove osgi-activator component to use whiteboard pattern
> I removed osgi-activator component to use RouteBuilder extended/production 
> ready whiteboard pattern, using service property.
>
> 3. Introduction of CamelContextConfigurer whiteboard
> Camel-core-osgi now provided CamelContextConfigurer interface allowing you to 
> create and configure CamelContext smoothly.
>
> 4. Deployer
> Now, you can directly deploy route in groovy or package as pure jar (no need 
> to be a bundle).
>
> 5. Karamel tool
> I started a new tool named karamel (Karaf with camel), exposed as CLI, Maven 
> plugin, Gradle plugin.
> Here’s some example of karamel CLI usage:
> - create ready to run karamel package and/or docker image:
>karamel build myroute.class
>karamel build myroute.xml
>karamel build myroute.groovy
> - run karamel package:
>   karamel run route1.jar route2.jar
>   karamel run route1.jar route2.xml
>   karamel run route1.groovy route2.xml
>   karamel run route1.xml mybundle.jar
>   karamel run route1.xml myfeature.xml
>
> 6. Improved and extended examples
> The camel-karaf-examples repository will be populated with concrete examples. 
> These examples will be used in test as part of the repo itself.
>
> I will submit several PRs.
>
> I will keep you posted.
>
> Regards
> JB
>


Re: [VOTE] Release Apache Camel 3.4.0 with Spring Boot and Karaf Support Projects

2020-06-18 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 15/06/2020 à 09:14, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.4.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 118
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12348216=12311220
>
> == Apache Camel 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1220/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1220/org/apache/camel/apache-camel/3.4.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.4.0
>
> == Apache Camel Spring Boot 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1221/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.4.0
>
> == Apache Camel Karaf 3.4.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1222/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.4.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.4.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.3.0 with Spring Boot and Karaf Support Projects

2020-05-11 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 11/05/2020 à 12:48, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.3.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 149
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12347798=12311211
>
> == Apache Camel 3.3.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1211/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1211/org/apache/camel/apache-camel/3.3.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.3.0
>
> == Apache Camel Spring Boot 3.3.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1213/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.3.0
>
> == Apache Camel Karaf 3.3.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1212/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.3.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.3.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.25.1

2020-04-13 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 13/04/2020 à 09:26, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.25.1, a new patch release for
> the 2.25.x branch with 14 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346872=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1204/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1204/org/apache/camel/apache-camel/2.25.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.25.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.25.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [JIRA] - Camel-Karaf

2020-04-06 Thread Francois Papon
Ok, I missed them.

May be we can merge OSGi and Karaf jira components?

regards,

François
fpa...@apache.org

Le 06/04/2020 à 15:33, Jean-Baptiste Onofre a écrit :
> We already have osgi/karaf component in Camel jira.
>
> We can eventually rename it to be "straighter" and more karaf/winegrower 
> generic.
>
> Regards
> JB
>
>> Le 6 avr. 2020 à 15:30, Francois Papon  a 
>> écrit :
>>
>> Hi,
>>
>> Is there a plan to create a camel-karaf component in Jira?
>>
>> As Camel-Karaf has a dedicated git repository, may be it could be easier to 
>> follow related issues.
>>
>> Thoughts?
>>
>> regards,
>>
>> -- 
>> François
>> fpa...@apache.org
>>


[JIRA] - Camel-Karaf

2020-04-06 Thread Francois Papon
Hi,

Is there a plan to create a camel-karaf component in Jira?

As Camel-Karaf has a dedicated git repository, may be it could be easier to 
follow related issues.

Thoughts?

regards,

-- 
François
fpa...@apache.org



Re: [VOTE] Release Apache Camel 3.2.0 with Spring Boot and Karaf Sub-Projects

2020-04-02 Thread Francois Papon
+1 (non-binding)

Thanks guys for the great job!

regards,

François
fpa...@apache.org

Le 02/04/2020 à 11:53, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.2.0 (with Apache Camel Spring
> Boot and Apache Camel Karaf), a new minor release with 160
> improvements and fixes.
>
> Please note that Karaf support has been moved into a separate repository [1].
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346956=12311211
>
> == Apache Camel 3.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1190/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1190/org/apache/camel/apache-camel/3.2.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.2.0
>
> == Apache Camel Spring Boot and Karaf 3.2.0 ==
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1191/
>
> Please note that Camel Spring Boot and Camel Karaf have been deployed
> to the same staging repository. This should not be a problem as we are
> planning to release everything in one flush. Next time we will make
> sure to create separate release repositories.
>
> Tags:
> - 
> https://gitbox.apache.org/repos/asf?p=camel-spring-boot.git;a=tag;h=refs/tags/camel-spring-boot-3.2.0
> - 
> https://gitbox.apache.org/repos/asf?p=camel-karaf.git;a=tag;h=refs/tags/camel-karaf-3.2.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel, Camel Spring Boot and Camel
> Karaf 3.2.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>
> [1] https://github.com/apache/camel-karaf


Re: [VOTE] Release Apache Camel 2.25.0

2020-01-20 Thread Francois Papon
+1 (non-binding)

Tested with some local projects.

Thanks!

regards,

François
fpa...@apache.org

Le 20/01/2020 à 09:09, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.25.0, a new minor release for
> the 2.25.x branch with 112 improvements and fixes. Please note that
> Camel 2.25.x is the last minor release for Camel 2.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345517=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1172/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1172/org/apache/camel/apache-camel/2.25.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.25.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.25.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: Camel Banner for FOSDEM

2020-01-16 Thread Francois Papon
Very nice!

regards,

François
fpa...@apache.org

Le 16/01/2020 à 17:33, Christina Lin a écrit :
> Looks like the attachment didn't come through, here is the link to
> view the banner. 
> https://drive.google.com/file/d/1V45W_d1V5tlZSBok8jAWDyfKCXVfKqIq/view?usp=sharing
>
> On Thu, Jan 16, 2020 at 11:26 AM Christina Lin  > wrote:
>
> Hey everyone, 
>
> I am working on a rollup banner for the upcoming FOSDEM event,
> wanted to run it through with the community before I go ahead and
> print it. This will be used in the booth. Let me know what you
> think! Thanks! 
>
> preview.png
>
> Thanks,
> Christina Lin
>


Re: [VOTE] Release Apache Camel 3.0.1

2020-01-13 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 12/01/2020 à 19:55, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.1, the first patch release
> for the 3.0.x branch with 41 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346544=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1170/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1170/org/apache/camel/apache-camel/3.0.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [DISCUSS] - camel-examples git repository

2019-12-19 Thread Francois Papon
It make senses :)

big +1

regards,

François
fpa...@apache.org

Le 19/12/2019 à 09:55, Claus Ibsen a écrit :
> Hi
>
> I would like to create a new git repository that only holds our Camel 
> examples.
>
> camel-examples
>
>
> JIRA:
> https://issues.apache.org/jira/browse/CAMEL-13830
>
>
> This has among others the following benefits
>
> 1)
> Easier to find examples (we also add better navigation to it from website)
> One place to look for examples
>
> 2)
> Easy to download and get started.
>
> It's not a massive set of code, as its just examples.
> Its built against a released versions out of the box, so you can clone
> or download via github etc and get started asap, as the example dont
> need to build source code first but just downloads the needed JARs and
> runs.
>
> 3)
> Its easier for contributors to contribute new examples. Not a massive
> code base to manage.
>
> 4)
> Makes us build examples that are using Camel BOM and don't get tied to
> apache camel source code via parent pom.xml or others that makes it
> harder to copy/paste an example for end users to tweak and use on his
> own.
>
> 5)
> We can include examples across our camel repositories, kafka,
> spring-boot, quarkus, karaf, etc.
>
> 6)
> Reduce build time on other Camel repositories as they dont have
> examples as part of their regular build.
>
>
>
>
>


Re: [VOTE] Release Apache Camel Quarkus 1.0.0-M1

2019-12-06 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 04/12/2019 à 13:06, Andrea Cosentino a écrit :
> Hello all:
>
> This is a vote to release Apache Camel Quarkus 1.0.0-M1
>
> This release contains new extensions, bug fixes and has been updated to 
> Quarkus 1.0.1.Final and Camel 3.0.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1165/
>
> Tag:
> https://gitbox.apache.org/repos/asf?p=camel-quarkus.git;a=tag;h=d7ad515770c2e95b4d46223877f8e1eddfc98d85
>
> Source release package:
> https://repository.apache.org/content/repositories/orgapachecamel-1165/org/apache/camel/quarkus/camel-quarkus-parent/1.0.0-M1/camel-quarkus-parent-1.0.0-M1-source-release.zip
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel Quarkus 1.0.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Andrea
>
>
> --
> Andrea Cosentino 
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd


Re: camel-kafka-connector

2019-11-28 Thread Francois Papon
It would be very nice to have this as a subproject in Camel!

regards,

François
fpa...@apache.org

Le 27/11/2019 à 23:48, Andrea Tarocchi a écrit :
> Hi,
>
> In the past months, some folks at Red Hat have been working on the
> integration between Apache Camel and Kafka Connect.
> Kafka Connect, an open source component of Kafka, is a framework for
> connecting Kafka with external systems and in a nutshell to inject
> data in and out of a Kafka broker [1].
>
> The result of the polishing of the initial PoC is available in the
> camel-kafka-connector repository [2].
>
> I do believe that making camel appealing to be used directly inside
> the Kafka ecosystem would be beneficial for our community. Providing
> unmatched external system connectivity capabilities to Kafka would
> expand the use of camel in the streaming world.
>
> So I’m proposing to officially support camel-kafka-connect as an
> Apache Camel’s main
> subproject that could be regarded as a new platform along with those
> we support as today (Spring Boot, Karaf and recently Quarkus).
>
> The original contributors, on behalf of which I speak, are keen to
> donate the code hosted in the repository at [2] to the Apache Software
> foundation.
>
> Thoughts ?
>
> Andrea Tarocchi.
> Andrea Cosentino.
>
> [1] https://kafka.apache.org/documentation/#connect
> [2] https://github.com/jboss-fuse/camel-kafka-connector
>


Re: Integration stand at FOSDEM

2019-11-25 Thread Francois Papon
Hi,

+1 for me too :)

I would be more than happy to participate.

regards,

François
fpa...@apache.org

Le 25/11/2019 à 16:22, Jean-Baptiste Onofré a écrit :
> Hi Zoran,
>
> I plan to be there as well !
>
> I would like to present an update about Camel on Karaf/Cloud if it works
> for you guys.
>
> Regards
> JB
>
> On 21/11/2019 12:43, Zoran Regvart wrote:
>> Hi Cameleers,
>> FOSDEM organizers have announced the acceptance of the "Integration
>> Process Community" stand[1]. Stands are good opportunity to spread the
>> word about Camel, meet and talk to the community. FOSDEM stands in
>> particular, in my experience, receive a high foot traffic.
>>
>> I'm planning on going to FOSDEM and I can man the stand and represent
>> Apache Camel there.
>>
>> If you wish to participate in the stand please come forward. Also if
>> you have any ideas or suggestions, for example: material that could be
>> presented there.
>>
>> zoran
>>
>> [1] https://fosdem.org/2020/news/2019-11-19-accepted-stands/
>>


Re: [VOTE] Release Apache Camel 3.0.0

2019-11-25 Thread Francois Papon
+1 (non-binding)

Tested with Apache Karaf 4.2.7

Thanks!

regards,

François
fpa...@apache.org

Le 25/11/2019 à 09:45, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0, a new major release with
> 1012 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1164/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1164/org/apache/camel/apache-camel/3.0.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.0.0-RC3 (Release Candidate 3)

2019-10-21 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 21/10/2019 à 09:00, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-RC3 (Release Candidate
> 3), the third release candidate towards a new Camel 3.0.0 major
> release with another 48 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12346354=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1158/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1158/org/apache/camel/apache-camel/3.0.0-RC3/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-RC3
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-RC3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.0.0-RC2 (Release Candidate 2)

2019-10-02 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 02/10/2019 à 09:19, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-RC2 (Release Candidate
> 2), the second release candidate towards a new 3.0.0 major release
> with another 94 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345998=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1154/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1154/org/apache/camel/apache-camel/3.0.0-RC2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-RC2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-RC2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.23.4

2019-09-16 Thread Francois Papon
+1 (non-binding)

Tested with some personal projects.

Thanks!

regards,

François
fpa...@apache.org

Le 16/09/2019 à 09:12, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.4, a new patch release for
> the camel 2.23.x branch with18 improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345671=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1151/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1151/org/apache/camel/apache-camel/2.23.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.23.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.24.2

2019-09-10 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 09/09/2019 à 09:22, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.24.2, the second patch
> release for the camel-2.24.x branch with 20 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345672=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1150/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1150/org/apache/camel/apache-camel/2.24.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.24.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.24.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 3.0.0-RC1 (Release Candidate 1)

2019-08-28 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 27/08/2019 à 08:51, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-RC1, the first release
> candidate towards a new 3.0.0 major release with 148 improvements and
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345723=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1149/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1149/org/apache/camel/apache-camel/3.0.0-RC1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-RC1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-RC1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [DISCUSS] New Camel website, rump up to go live

2019-08-20 Thread Francois Papon
Thanks Zoran!

regards,

François
fpa...@apache.org

Le 20/08/2019 à 10:35, Zoran Regvart a écrit :
> Hi Cameleers,
> some time has passed and I guess we haven't found any blocking issues
> preventing the website launch.
>
> With that I'm going to contact INFRA and ask for two things:
>  - publishing from the `asf-git` branch of the `camel-website` to the
> root of the website (instead of the `/staging`), in effect launching
> the new website
>  - disabling/removing the build bot build[1] for the old Camel website
>
> Thanks :)
>
> zoran
>
> [1] https://ci.apache.org/builders/camel-site-production
>
> On Thu, Aug 1, 2019 at 11:18 AM Zoran Regvart  wrote:
>> Hi Cameleers,
>> so it's been a while since we discussed the state of the new website,
>> so let me start by enumerating what we have done so far and then what
>> I think needs to be done for the website to go live.
>>
>> So what has been done:
>>
>> A lot. A lot of folk over almost two years helped with the website
>> effort and their help needs to be acknowledged. I'm sorry not to
>> mention everyone here as I would certainly forget someone. I do wish
>> to thank you all for your contributions.
>>
>> In points:
>>  - content from the Confluence wiki has been (high 90% of it) cleaned
>> up and migrated to asciidoc format and is now maintained in the git
>> repository
>>  - tools that maintain the documentation were developed (updating from
>> javadoc, moving/copying documents and maintaining indexes)
>>  - initial website design was contributed and polished over time
>>  - tools to build and develop the website were implemented and
>> integrated with the CI
>>  - a lot of small paper-cut issues were resolved
>>
>> You can find the majority of these issues as subtasks of CAMEL-11492[1].
>>
>> What I think needs to be done:
>>  - gather more feedback on the staging website
>> (https://camel.apache.org/staging/)
>>  - find/resolve any search engine issues (such as CAMEL-13800[2])
>>
>> What I think would be good to do:
>>  - more search engine optimization (like the microdata effort CAMEL-11494[3])
>>  - I'd like to polish the documentation a bit CAMEL-13780[3], if it
>> turns out not too much work split up the documentation into even
>> further modules (CAMEL-13812[4])
>>  - add search (CAMEL-11503)
>>  - iron out any design/responsive layout issues
>>
>> I think we can work on the 'needs to be done' bits in the following
>> week and rump up the effort to replace the old website with the new
>> one currently present only on the staging.
>>
>> And depending on the feedback, that is if there are no large blocking
>> issues found, I think we can go live with the new website somewhere in
>> the middle of August.
>>
>> So, with that I would like to call to action, I'd like to have a list
>> of actionable issues we need to resolve for the go live of the new
>> website.
>>
>> If you can take a moment and have a look at the staging site
>> (https://camel.apache.org/staging/) and either by replying on the
>> thread or by creating a subtask on CAMEL-11492[1] with any issues that
>> you think need to be addressed before we go live.
>>
>> And, if you can contribute to this effort, by modifying the design,
>> improving the build tools, correcting the documentation please feel
>> free to do so.
>>
>> zoran
>>
>> [1] https://issues.apache.org/jira/browse/CAMEL-11492
>> [2] https://issues.apache.org/jira/browse/CAMEL-13800
>> [3] https://issues.apache.org/jira/browse/CAMEL-11494
>> [4] https://issues.apache.org/jira/browse/CAMEL-13780
>> [5] https://issues.apache.org/jira/browse/CAMEL-13812
>> [6] https://issues.apache.org/jira/browse/CAMEL-11503
>>
>> --
>> Zoran Regvart
>
>


Re: [CAMEL-11503] Add search

2019-08-12 Thread Francois Papon
Hi Nayananga,

I have not started working yet on this, I just take a look on some
potential solutions like https://lunrjs.com/

Sorry but I don't have enough free time to work on it now and you can
take it if you want ;)

regards,

François
fpa...@apache.org

Le 12/08/2019 à 10:16, Nayananga Muhandiram a écrit :
> Hi all, I would like to know if Mr Francois Papon
> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fpapon> or
> anyone else working on this issue?
> Thank you. Regards
> Nayananga Anuradha Muhandiram
> Computer Science Undergraduate at  University of Jaffna
> M  +94716369541  <+94716369541>
> E  nayanangamuhandi...@gmail.com  
> <http://facebook.com/nayananga>
> <http://us.linkedin.com/in/nayanangamuhandiram>
> <http://twitter.com/nicknam95>
>


Re: [DISCUSS] New Camel website, rump up to go live

2019-08-01 Thread Francois Papon
Hi,

Agree, it would be nice if we could publish the new website this month :)

regards,

François
fpa...@apache.org

Le 01/08/2019 à 11:18, Zoran Regvart a écrit :
> Hi Cameleers,
> so it's been a while since we discussed the state of the new website,
> so let me start by enumerating what we have done so far and then what
> I think needs to be done for the website to go live.
>
> So what has been done:
>
> A lot. A lot of folk over almost two years helped with the website
> effort and their help needs to be acknowledged. I'm sorry not to
> mention everyone here as I would certainly forget someone. I do wish
> to thank you all for your contributions.
>
> In points:
>  - content from the Confluence wiki has been (high 90% of it) cleaned
> up and migrated to asciidoc format and is now maintained in the git
> repository
>  - tools that maintain the documentation were developed (updating from
> javadoc, moving/copying documents and maintaining indexes)
>  - initial website design was contributed and polished over time
>  - tools to build and develop the website were implemented and
> integrated with the CI
>  - a lot of small paper-cut issues were resolved
>
> You can find the majority of these issues as subtasks of CAMEL-11492[1].
>
> What I think needs to be done:
>  - gather more feedback on the staging website
> (https://camel.apache.org/staging/)
>  - find/resolve any search engine issues (such as CAMEL-13800[2])
>
> What I think would be good to do:
>  - more search engine optimization (like the microdata effort CAMEL-11494[3])
>  - I'd like to polish the documentation a bit CAMEL-13780[3], if it
> turns out not too much work split up the documentation into even
> further modules (CAMEL-13812[4])
>  - add search (CAMEL-11503)
>  - iron out any design/responsive layout issues
>
> I think we can work on the 'needs to be done' bits in the following
> week and rump up the effort to replace the old website with the new
> one currently present only on the staging.
>
> And depending on the feedback, that is if there are no large blocking
> issues found, I think we can go live with the new website somewhere in
> the middle of August.
>
> So, with that I would like to call to action, I'd like to have a list
> of actionable issues we need to resolve for the go live of the new
> website.
>
> If you can take a moment and have a look at the staging site
> (https://camel.apache.org/staging/) and either by replying on the
> thread or by creating a subtask on CAMEL-11492[1] with any issues that
> you think need to be addressed before we go live.
>
> And, if you can contribute to this effort, by modifying the design,
> improving the build tools, correcting the documentation please feel
> free to do so.
>
> zoran
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11492
> [2] https://issues.apache.org/jira/browse/CAMEL-13800
> [3] https://issues.apache.org/jira/browse/CAMEL-11494
> [4] https://issues.apache.org/jira/browse/CAMEL-13780
> [5] https://issues.apache.org/jira/browse/CAMEL-13812
> [6] https://issues.apache.org/jira/browse/CAMEL-11503
>


Re: [VOTE] Release Apache Camel K 1.0.0-M1 and Runtime 1.0.0

2019-07-26 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 26/07/2019 à 10:22, Nicola Ferraro a écrit :
> Hello all:
>
> This is a combined vote to release Apache Camel K 1.0.0-M1 and Apache Camel
> K Runtime 1.0.0.
>
> Apache Camel K Runtime versions follow a different convention (without
> milestones) and won't necessarily match main Camel K versions in the future.
>
> Runtime staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1145
> Runtime Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=shortlog;h=refs/tags/camel-k-runtime-parent-1.0.0
>
> Camel K staging repository:
> https://dist.apache.org/repos/dist/dev/camel/camel-k/1.0.0-M1/
> Camel K Tag:
> https://gitbox.apache.org/repos/asf?p=camel-k.git;a=shortlog;h=refs/tags/1.0.0-M1
>
> Staging container image repository:
> https://hub.docker.com/r/camelk/camel-k/tags
>
> It's possible to install all staging artifacts with a single command:
> kamel install --operator-image=camelk/camel-k:1.0.0-M1 --maven-repository=
> https://repository.apache.org/content/repositories/orgapachecamel-1145
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel K 1.0.0-M1 and Apache Camel K
> Runtime 1.0.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Nicola Ferraro
>


Re: [HEADS UP] - camel3 - camel-http4 renaming to camel-http

2019-07-25 Thread Francois Papon
Agree, it make sense!

regards,

François
fpa...@apache.org

Le 25/07/2019 à 12:23, Tadayoshi Sato a écrit :
> +1
>
> Maybe it's also good time to review other components that have similar
> variants.
>
> On Thu, Jul 25, 2019 at 7:09 PM Alex Dettinger 
> wrote:
>
>> +1
>>
>> On Thu, Jul 25, 2019 at 12:02 PM Andrea Cosentino 
>> wrote:
>>
>>> +1
>>>
>>> Il giorno gio 25 lug 2019 alle ore 11:48 Claus Ibsen <
>>> claus.ib...@gmail.com>
>>> ha scritto:
>>>
 Hi

 So what has been bothering Camel 2.x users is that when they use http
 they would likely use the camel-http4 component and then they should
 use http4 as the component name. The old camel-http component is
 deprecated as the http client it uses is EOL for many many years.

 So with Camel 3 on the way we have deleted the old camel-http
 component and the camel-http4 component now has both http and http4 as
 component names.

 I think we should rename the camel-http4 back to camel-http and then
 favour using http as the component name, and then deprecate http4 (or
 even remove it).

 Any thoughts?


 --
 Claus Ibsen
 -
 http://davsclaus.com @davsclaus
 Camel in Action 2: https://www.manning.com/ibsen2



Re: [HEADSUP] Documentation link checker in the build

2019-07-23 Thread Francois Papon
Well done Nayananga!

Great job!

regards,

François
fpa...@apache.org

Le 23/07/2019 à 20:10, Zoran Regvart a écrit :
> Hi Cameleers,
> I've added a `xref-validator`[1] to the `docs` module[2], this will
> fail the build if there's a `xref` link in the asciidoc files (.adoc)
> that cannot be resolved -- colloquially: broken link.
>
> There's been a great effort by Nayananga our GSoC student helping with
> the website on getting all the links pointing to the right places and
> it's really easy to mistype a `xref` link, so that's why I've added it
> as a part of the CAMEL-13589[3].
>
> Now, you might be wondering what are `xref` links and how to prevent
> them from becoming broken. For Antora, the tool that converts the
> asciidoc files to html, we need to specify all links between asciidoc
> files as `xref:` links, previously you might have seen `link:` being
> used.
>
> There's a good explanation of this concept of page ID in the Antora
> documentation[4] and how to link between two pages using `xref:`
> links[5].
>
> For now remember that if you're pointing to the documentation within
> the same Antora component, and we have two such components `manual`[6]
> and `components`[7], use the form `xref:document.adoc`; and between
> two Antora components use the form `xref:component::document.adoc`.
>
> For example, the cdi.adoc is within the `components` component and
> when it needs to link to a `camel-maven-archetypes.adoc` in the
> `manual` component the xref needs to look like:
>
> xref:manual::camel-maven-archetypes.adoc[Maven archetypes]
>
> Have a look at the example[8] in the git repository.
>
> So to test if the xrefs are valid you can run:
>
> $ ./mvnw -f docs verify
>
> It only takes about 1 minute or so to run.
>
> Feel free to reach out to me if you have any questions on this.
>
> zoran
>
> [1] https://gitlab.com/antora/xref-validator
> [2] 
> https://github.com/apache/camel/blob/a607098a51cdde9eb87bf8dcc61c9428dd771dd4/docs/pom.xml#L85-L96
> [3] https://issues.apache.org/jira/browse/CAMEL-13589
> [4] https://docs.antora.org/antora/2.0/page/page-id/
> [5] https://docs.antora.org/antora/2.0/asciidoc/page-to-page-xref/
> [6] 
> https://github.com/apache/camel/tree/master/docs/user-manual/modules/ROOT/pages
> [7] 
> https://github.com/apache/camel/tree/master/docs/components/modules/ROOT/pages
> [8] 
> https://github.com/apache/camel/blob/a607098a51cdde9eb87bf8dcc61c9428dd771dd4/docs/components/modules/ROOT/pages/cdi.adoc#L1071


Re: [VOTE] Release Apache Camel 3.0.0-M4 (Milestone 4)

2019-07-09 Thread Francois Papon
+1 (non-binding)

Thanks for the release!

regards,

François
fpa...@apache.org

Le 07/07/2019 à 11:16, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-M4 (Milestone 4), the
> fourth milestone towards a new 3.0.0 major release with another 105
> improvements and fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345567=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1143/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1143/org/apache/camel/apache-camel/3.0.0-M4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-M4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.24.1

2019-06-20 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 20/06/2019 à 23:04, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.24.1, the first patch release
> for the camel-2.24.x branch with 22 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345495=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1142/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1142/org/apache/camel/apache-camel/2.24.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.24.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.24.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.22.5

2019-06-10 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François
fpa...@apache.org

Le 08/06/2019 à 16:52, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.5 the last planned patch
> release for the camel-2.22.x branch with 13 improvements and bug
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345404=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1140/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1140/org/apache/camel/apache-camel/2.22.5/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.5
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.5
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE]

2019-06-04 Thread Francois Papon
Hi Jason,

Thanks for your great job!

Is there a way to generate a css from the styleguide ?

Regards,

François
fpa...@apache.org

Le 05/06/2019 à 00:16, Jason Brock a écrit :
> Hello again everyone,
> (Please let me know if this requires a new thread)
>
> Here's the next round of work for comparison, debate, and/or voting.
>
> I'm including the current homepage and layout because there is value in the
> work that has been done and each change deserves careful consideration to
> make sure that it's worth changing.
>
> Previously established resources:
> https://design.jboss.org/camel/website/mockups/images/00-Colorpalette.png
> https://design.jboss.org/camel/website/mockups/images/00-Styleguide.png
>
> The Current Homepage (unaltered screenshot)
> https://design.jboss.org/camel/website/mockups/images/01-Current-Homepage.png
>
> The Current Homepage with new styles applied
> https://design.jboss.org/camel/website/mockups/images/02-CurrentLayouy-NewStyle.png
>
> A new concept for layout and design
> https://design.jboss.org/camel/website/mockups/images/03-NewLayout-NewStyle.png
>
> The working file for Adobe XD in case anyone wants to peak under the hood
> and tinker a bit.
> https://design.jboss.org/camel/website/mockups/working/Camel-Homepage.xd
>
> All the best,
>
> Jason Brock
>
> Web UX Designer, Middleware Engineering Services
>
> Red Hat Austin, Texas 
>
> He, Him, & His | jbr...@redhat.com | 512-786-8304
> 
>
>
> On Mon, May 20, 2019 at 5:58 PM Jason Brock  wrote:
>
>> Hi Claus!
>>
>> I'm currently on PTO but I will have some time next week to focus on the
>> Apache Wireframes.
>>
>> Jason Brock
>>
>> Web UX Designer, Middleware Engineering Services
>>
>> Red Hat Austin, Texas 
>>
>> He, Him, & His | jbr...@redhat.com | 512-786-8304
>> 
>>
>>
>> On Thu, May 16, 2019 at 10:23 AM Claus Ibsen 
>> wrote:
>>
>>> Hi Jason
>>>
>>> How is it going with the next step of the Camel website mockup and style?
>>>
>>> On Thu, May 2, 2019 at 6:53 PM Jason Brock  wrote:
 The next step is to take those styles and build a mockup of an existing
 page (probably the home page) while at the same time also exploring
>>> ways to
 improve navigation and content arrangement. Considering the nature of
>>> the
 Apache voting/collaboration system I think it's a good idea to compare
 three images side-by-side:

1. A snapshot of the current home page
2. A version of the current homepage with only the visual styles
>>> changed
(UI Only)
3. A new homepage with a new layout, new navigation, and the new
>>> styles
(UX and UI)

 Then we can hold an open discussion and everyone can vote.

 In a typical workflow, my team creates designs in Adobe XD and we share
 public links to mockups so anyone can test and comment. We usually don't
 share the source files simply because no one has ever really cared to
>>> look
 at them. But there's no reason we can't share them and let anyone who
>>> wants
 to download Adobe XD
 <
>>> https://www.adobe.com/products/xd.html?sdid=12B9F15S=Search_id=EAIaIQobChMI3c78wpj94QIVi4bACh0lowF9EAAYASAAEgJqgPD_BwE:G:s_kwcid=AL!3085!3!315233774103!b!!g!!adobe%20xd%20free
 make
 changes and peak under the hood. (Adobe does not charge people to use
 XD)figma

 We could also explore using something like Figma <
>>> https://www.figma.com/>
 that isn't free, but offers a browser based design tool so anyone on any
 platform can make edits - but it's a SaaS so we'd have to find a
>>> sponsor.
 I don't know that traditional design workflows and the Apache
>>> collaboration
 methodology have ever really crossed paths before, so this could be a
 really amazing time to try out some new stuff. I'm open to suggestions
>>> and
 alternatives.

 All the best,

 JASON K BROCK

 Web UX DESIGNER, MIDDLEWARE ENGINEERING SERVICES

 Red Hat - Austin, TX  | jbr...@redhat.com |
 512-786-8304


 On Thu, May 2, 2019 at 10:32 AM Claus Ibsen 
>>> wrote:
> Hi
>
>
> On Thu, May 2, 2019 at 4:39 PM Andrea Cosentino
>  wrote:
>> Hello all,
>>
>> I think we can go ahead with the design number one.
>>
> Yes I also think so.
>
> Jason what would be the next step?
>
>> --
>> Andrea Cosentino
>> --
>> Apache Camel PMC Chair
>> Apache Karaf Committer
>> Apache Servicemix PMC Member
>> Email: ancosen1...@yahoo.com
>> Twitter: @oscerd2
>> Github: oscerd
>>
>>
>>
>>
>>
>>
>> On Tuesday, April 30, 2019, 5:30:19 PM GMT+2, Andrea Cosentino <
> anco...@gmail.com> wrote:
>>
>>
>>
>>
>> I think we can give 24 hours to jump in for vote, then we can go
>>> ahead
> :-)
>> Il 

Re: [VOTE] Release Apache Camel 2.24.0

2019-05-07 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 07/05/2019 à 11:30, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.24.0, a new minor release
> with 156 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344459=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1136/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1136/org/apache/camel/apache-camel/2.24.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.24.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.24.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE]

2019-05-04 Thread Francois Papon
Hi,

I missed this thread...number 1 is very nice!

Thanks for the great work Jason :)

regards,

François Papon
fpa...@apache.org

Le 30/04/2019 à 19:20, Jason Brock a écrit :
> So far we have
>
> 11 Votes for Number 1
> 0 Votes for Number 2
> 3 Votes for Number 3
>
> It sounds like there is a bit of a preference for light and clean design
> without too much ornamentation. Personally, I think this is a good choice -
> your content should be supported by the design, not competing with it for
> attention.
>
> Does anyone else want to weigh in? Or should we start on wireframing the
> content?
>
> All the best,
>
> JASON K BROCK
>
> Web UX DESIGNER, MIDDLEWARE ENGINEERING SERVICES
>
> Red Hat - Austin, TX  | jbr...@redhat.com |
> 512-786-8304
>
>
> On Mon, Apr 29, 2019 at 3:19 AM Zoran Regvart  wrote:
>
>> Hi Jason,
>> thank you for creating these design concepts. If my aesthetics were
>> relevant in any way: the first design concept feels a simple and
>> elegant to me.
>>
>> zoran
>>
>> On Tue, Apr 23, 2019 at 5:15 PM Jason Brock  wrote:
>>> Hello everyone!
>>>
>>> Here is a first round of design concepts to help refresh the look and
>> feel
>>> of the Apache Camel website. Please let me know if you require a
>> particular
>>> file format and I will furnish that to the group.
>>>
>>> Concept One:
>>>
>> https://design.jboss.org/camel/website/styleguides/images/01-colorpalette.png
>> https://design.jboss.org/camel/website/styleguides/images/01-styleguide.png
>>> Concept Two:
>>>
>> https://design.jboss.org/camel/website/styleguides/images/02-colorpalette.png
>> https://design.jboss.org/camel/website/styleguides/images/02-styleguide.png
>>> Concept Three:
>>>
>> https://design.jboss.org/camel/website/styleguides/images/03-colorpalette.png
>> https://design.jboss.org/camel/website/styleguides/images/03-styleguide.png
>>>
>>> All the best,
>>>
>>> JASON K BROCK
>>>
>>> Web UX DESIGNER, MIDDLEWARE ENGINEERING SERVICES
>>>
>>> Red Hat - Austin, TX  | jbr...@redhat.com |
>>> 512-786-8304
>>
>>
>> --
>> Zoran Regvart
>>


Re: [VOTE] Release Apache Camel 2.22.4

2019-04-08 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 08/04/2019 à 09:34, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.4, the fourth patch
> release for the camel-2.22.x branch with 26 improvements and bug
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344887=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1127/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1127/org/apache/camel/apache-camel/2.22.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.23.2

2019-04-07 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 07/04/2019 à 10:39, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.2, the second patch
> release for the camel-2.23.x branch with 64 improvements and bug
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344839=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1125/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1125/org/apache/camel/apache-camel/2.23.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.23.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: Help with a task - Camel 11492

2019-04-05 Thread Francois Papon
Hi,

Thanks for you proposal ;)

You can work on the "news" and  "faq" parts.

You have to create a Hugo template for the rendering of the pages.

regards,

François Papon
fpa...@apache.org

Le 05/04/2019 à 07:02, Muhammad Khasail a écrit :
> Hi,
> I'm reaching out since I was interested in helping out with the Camel
> Website project.
>
> I can produce any and all kinds of content as long as its in the English
> language. However, I was hoping to get involved with coding, since that's
> what I'm studying for and hoping to choose as a career path.
>
> Let me know what you think.
> Waiting to hear back.
>
>
>
> *Regards*
>
>
> *M.Khasail+92-320-5011-329 *
>



Re: [VOTE] Release Apache Camel 3.0.0-M2 (Milestone 2)

2019-03-27 Thread Francois Papon
+1 (non-binding)

Thanks!

Regards,

François Papon
fpa...@apache.org

Le 26/03/2019 à 00:50, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-M2, the second milestone
> towards a new 3.0.0 major release with currently 471 improvements and
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1124/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1124/org/apache/camel/apache-camel/3.0.0-M2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-M2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: A new vision for the Apache Camel Website

2019-03-07 Thread Francois Papon
Hi guys,

It's cool to have more contributions on the website ;)

I'm not a web design professional so don't hesitate to suggest!

regards,

François Papon
fpa...@apache.org

Le 07/03/2019 à 13:46, Zoran Regvart a écrit :
> Hi Jason,
> thank you for offering to help with the website. Please make sure that
> you subscribe to the dev@ mailing list (send an e-mail to
> dev-subscr...@camel.apache.org), I needed to approve this e-mail from
> the moderation queue.
>
> We have an open issue outlining the tasks for the new website at
> CAMEL-11492[1], can you go thought that and commend or create more
> issues for the tasks you outline. I suggest that we track who's doing
> what there and discus the details on the dev@ mailing list.
>
> What we have currently is a staging website that is built from
> apache/camel-website[2] git repository and there's a Jenkins build
> that builds the website and publishes it to staging[3]. I'm also
> trying to replace the Jenkins build with GitHub actions, there's a
> discussion I started on that[4] yesterday.
>
> We are also participating in Google Summer of Code for 2019 and we
> have one student applicant (cc-ed Nayananga Muhandiram) interested in
> helping with the website[5][6].
>
> The design and much of the implementation we currently have was done
> by Francois. I'll let Francois, Nayananga and you discuss on how to
> collaborate, I would suggest that exchanging ideas on the mailing
> list. to me it seems like the best way to do that.
>
> For myself, I can help with the infrastructure work (builds,
> scripting, coordinating with INFRA), and I can meddle with HTML/(bit)
> CSS/layout templates, I would leave the design to the professionals.
>
> thanks :)
>
> zoran
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11492
> [2] https://github.com/apache/camel-website
> [3] https://camel.apache.org/staging/
> [4] 
> https://mail-archives.apache.org/mod_mbox/camel-dev/201903.mbox/%3CCABD_Zr-sTi0BQqCnxbE%3D%3DsCuivQ%2BTsx1LZ8_%3DqNGQTVOg4ZENw%40mail.gmail.com%3E
> [5] 
> https://mail-archives.apache.org/mod_mbox/camel-dev/201903.mbox/%3CCAM5A4daJJF9RzVLbSeRecbOhmFT-hqiE5jE%2BkW9VkS_YZkd3kw%40mail.gmail.com%3E
> [6] https://issues.apache.org/jira/browse/CAMEL-11494
>
>
> On Thu, Mar 7, 2019 at 10:24 AM Jason Brock  wrote:
>> Hello Everyone!
>>
>> My name is Jason Brock and I'm a Web UX and Visual Designer at Red Hat.
>> With your permission and participation I'd like to offer my skills and
>> experience to help update and improve the Apache Camel Website.
>>
>> In the interest of total transparency, my process for open-source project
>> websites usually looks like this:
>>
>>1. Style Tiles
>>   - We deliver a small selection (3-5) style tiles, to establish
>>   guidelines for a visual design language
>>   - You nice folks evaluate those suggestions and provide feedback.
>>   Maybe you hold a vote. Maybe you have a discussion with feedback
>> and change
>>   requests. That part is up to your project team.
>>   - We deliver a revised/style tile for review.
>>   - Repeat as necessary.
>>   2. Architecture
>>   - We deliver a proposal for information architecture. Usually a
>>   visual map of the site that shows how many pages there are, how they're
>>   connected, and a high-level overview of what kinds of content exist 
>> there.
>>   - The community evaluates our design and provides feedback
>>   - We revise...
>>   - Repeat as necessary.
>>   3. Wireframes (sometimes we can skip straight to Mockups if things
>>are moving along well)
>>   - We build some mid-resolution layouts of how the pages of the site
>>   will be arranged, usually black and white, not a lot of imagery, just
>>   getting the blocking right for page flow and functionality.
>>   - The community weighs in...
>>   - We revise...
>>   - Repeat as necessary.
>>   4. Mockups
>>   - We build high resolution mockups of the pages, intended to be used
>>   by front-end engineers to code against.
>>   - The community weighs in...
>>   - We revise...
>>   - Repeat until everyone is in agreement.
>>5. Coding
>>   - Could be interested community members, or our MWES engineers. Most
>>   likely a combination of both.
>>   - We help review the final product against the approved mockups
>>   - The community weighs in...
>>6. The site goes live!
>>   - We all celebrate
>>
>> Please feel free to reach out to me with any questions or concerns at any
>> time through this process, my aim is to support not dictate.
>>
>> (If there's a good IRC channel or public chat service that you like to use,
>> someone please let me know - I'll join and you can ping me there, too)
>>
>> All the best,
>>
>> JASON K BROCK
>>
>> Web UX DESIGNER, MIDDLEWARE ENGINEERING SERVICES
>>
>> Red Hat - Austin, TX  | jbr...@redhat.com |
>> 512-786-8304
>
>
> --
> Zoran Regvart


Re: [camel-3] - core OSGi / XML

2019-03-01 Thread Francois Papon
Ok,

I created the Jira:

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

I will push the PR for review.

Regards,

François Papon
fpa...@apache.org

Le 01/03/2019 à 14:50, Claus Ibsen a écrit :
> Hi
>
> Yeah but mind that moving them is not as easy, as the build assumes
> they are in the components folder. So you need to adjust
> camel-blueprint and camel-spring too, and also in the
> camel-package-maven-plugin some some code for dealing with these 2
> module names.
>
> I suggest to log a JIRA and then work on the PR
>
> On Fri, Mar 1, 2019 at 11:42 AM Francois Papon
>  wrote:
>> Ok,
>>
>> Can I push a PR for this?
>>
>> Regards,
>>
>> François Papon
>> fpa...@apache.org
>>
>> Le 01/03/2019 à 14:38, Claus Ibsen a écrit :
>>> Hi
>>>
>>> Yeah now that we have a core sub-folder, we can likely move them in there.
>>>
>>>
>>> On Fri, Mar 1, 2019 at 11:25 AM Francois Papon
>>>  wrote:
>>>> Hi,
>>>>
>>>> I see on master that this modules are under the "components" module:
>>>>
>>>> - camel-core-osgi
>>>>
>>>> - camel-core-xml
>>>>
>>>> Is there a reason to not put them under the "core" module?
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> François Papon
>>>> fpa...@apache.org
>>>>
>>>>
>
>



Re: [camel-3] - core OSGi / XML

2019-03-01 Thread Francois Papon
Ok,

Can I push a PR for this?

Regards,

François Papon
fpa...@apache.org

Le 01/03/2019 à 14:38, Claus Ibsen a écrit :
> Hi
>
> Yeah now that we have a core sub-folder, we can likely move them in there.
>
>
> On Fri, Mar 1, 2019 at 11:25 AM Francois Papon
>  wrote:
>> Hi,
>>
>> I see on master that this modules are under the "components" module:
>>
>> - camel-core-osgi
>>
>> - camel-core-xml
>>
>> Is there a reason to not put them under the "core" module?
>>
>> Regards,
>>
>> --
>> François Papon
>> fpa...@apache.org
>>
>>
>


[camel-3] - core OSGi / XML

2019-03-01 Thread Francois Papon
Hi,

I see on master that this modules are under the "components" module:

- camel-core-osgi

- camel-core-xml

Is there a reason to not put them under the "core" module?

Regards,

-- 
François Papon
fpa...@apache.org




Re: [VOTE] Release Apache Camel-K Runtime 0.3.0 (take 2)

2019-02-27 Thread Francois Papon
+1 (non-binding)

Thanks guys!

regards,

François Papon
fpa...@apache.org

Le 27/02/2019 à 12:30, Andrea Cosentino a écrit :
> Hello all:
>
> This is a vote to release Apache Camel-K runtime 0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1122
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=tag;h=2d5b34964e392f9c5f4b1a390f64af99de9079c2
> This release is important because it introduce the split between camel-k and 
> camel-k-runtime bits and also an initial support for Camel 3 M1.
>
> We have added the sources package too.
>
> Please test this release candidate and cast your vote.
>
> [ ] +1 Release the binary as Apache Camel-K 0.3.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Andrea
>
> --
> Andrea Cosentino 
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd


Re: [VOTE] Release Apache Camel-K Runtime 0.3.0

2019-02-26 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 26/02/2019 à 13:31, Andrea Cosentino a écrit :
> Hello all:
>
> This is a vote to release Apache Camel-K runtime 0.3.0
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1121/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel-k-runtime.git;a=tag;h=ffce60741685f5385c4923200cc8d8adf4a9eaac
>
> This release is important because it introduce the split between camel-k and 
> camel-k-runtime bits and also an initial support for Camel 3 M1.
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel-K 0.2.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Andrea
>
> --
> Andrea Cosentino 
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd


Re: [VOTE] Release Apache Camel 3.0.0-M1 (Milestone 1)

2019-02-18 Thread Francois Papon
+1 (non-binding)

Thanks for this great release!

Regards,

François Papon
fpa...@apache.org

Le 18/02/2019 à 11:22, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 3.0.0-M1, the first milestone
> towards a new 3.0.0 major release with currently 366 improvements and
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1119/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1119/org/apache/camel/apache-camel/3.0.0-M1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-M1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Camel 2.21.5

2019-02-03 Thread Francois Papon
+1 (non-binding)

Test on Karaf 4.2.2

Thanks!

Regards,

François Papon
fpa...@apache.org

Le 03/02/2019 à 13:48, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.5, a new patch release for
> the camel-2.21.x branch with 21 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344816=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1118/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1118/org/apache/camel/apache-camel/2.21.5/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.5
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.5
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: Camel FOSDEM BoF 2019

2019-01-29 Thread Francois Papon
Hi Zoran,

If I wasn't so far, I will be there!

Have a good session ;)

Regards,

François Papon
fpa...@apache.org

Le 29/01/2019 à 18:00, Zoran Regvart a écrit :
> Hi Camelers,
> I'd like to invite you to a Camel Birds of a Feather session at FOSDEM
> 2019 this Saturday, 2.2.2019. from 12:00 to 13:00 in the Room H.3242
> at Université libre de Bruxelles Campus du Solbosch, Brussels,
> Belgium.
>
> So anyone not already planning to go to FOSDEM this year, here's a
> good incentive to go :)
>
> Here's the link to the schedule:
>
> https://fosdem.org/2019/schedule/event/bof_apache_camel/
>
> For those not familiar with FOSDEM: Free and Open source Software
> Developers' European Meeting (FOSDEM) it's a two-day event organized
> by volunteers to promote the widespread use of free and open source
> software. It is the biggest free software  Entrance is completely
> free, there's no registration, you just need to show up.
>
> How to get there:
>
> https://fosdem.org/2019/practical/transportation/
>
> Hope to see you there :)
>
> zoran


Re: [VOTE] Release Apache Camel 2.22.3

2019-01-20 Thread Francois Papon
+1 (non-binding)

Thanks!

Regards,

François Papon
fpa...@apache.org

Le 19/01/2019 à 23:22, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.3, a new patch release for
> the camel-2.22.x branch with 44 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344398=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1117/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1117/org/apache/camel/apache-camel/2.22.3/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.3
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.23.1

2019-01-13 Thread Francois Papon
+1 (non-binding)

Thanks!

Regards,

François Papon
fpa...@apache.org

Le 12/01/2019 à 23:44, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.1, the first patch release
> for the camel-2.23.x branch with 33 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344567=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1116/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1116/org/apache/camel/apache-camel/2.23.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.23.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: [VOTE] Release Apache Camel 2.21.4

2019-01-07 Thread Francois Papon
+1 (non-binding)

Thanks!

Regards,

François Papon
fpa...@apache.org

Le 07/01/2019 à 12:18, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.4, the last planned patch
> release for the camel-2.21.x branch with 24 improvements and bug
> fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344344=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1115/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1115/org/apache/camel/apache-camel/2.21.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor


Re: Camel website

2018-12-18 Thread Francois Papon
Cool!

I will push a PR for the responsive soon.

Regards,

François Papon
fpa...@apache.org

Le 18/12/2018 à 15:51, Zoran Regvart a écrit :
> Thank you François, I merged your PR to camel-website master and it's
> now on staging:
>
> https://camel.apache.org/staging/
>
> looks pretty good :)
>
> zoran
>
> On Mon, Dec 17, 2018 at 11:19 AM Francois Papon
>  wrote:
>> Hi,
>>
>> Thanks for your feeback!
>>
>> For the mobile responsive, I didn't work on it yet but I keep it in mind ;)
>>
>> Regards,
>>
>> François Papon
>> fpa...@apache.org
>>
>> Le 17/12/2018 à 12:41, Andrea Cosentino a écrit :
>>> Really nice! Only that problem on mobile, but it looks great.
>>>
>>> --
>>> Andrea Cosentino
>>> --
>>> Apache Camel PMC Chair
>>> Apache Karaf Committer
>>> Apache Servicemix PMC Member
>>> Email: ancosen1...@yahoo.com
>>> Twitter: @oscerd2
>>> Github: oscerd
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Monday, December 17, 2018, 9:33:21 AM GMT+1, Onder SEZGIN 
>>>  wrote:
>>>
>>>
>>>
>>>
>>>
>>> Thanks François. It looks very nice.
>>> One minor comment:
>>> Look and feel is overlapping on mobile view. Maybe it could be adjusted to
>>> be more responsive.
>>>
>>> On Sun, Dec 16, 2018 at 3:59 PM Zoran Regvart  wrote:
>>>
>>>> Hi François,
>>>> I think that's awesome! Please do create a PR :)
>>>>
>>>> zoran
>>>> On Sat, Dec 15, 2018 at 7:28 PM Francois Papon
>>>>  wrote:
>>>>> Hi guys,
>>>>>
>>>>> I made some design integration on the website based on the new logo,
>>>>> it's not fully finished and it's just a proposal.
>>>>>
>>>>> You can have a preview about the home page here :
>>>>>
>>>>> https://openobject.fr/camel/
>>>>>
>>>>> If you like it I'm ready to push my PR and move forward with the
>>>>> documentation theme ;)
>>>>>
>>>>> Regards,
>>>>>
>>>>> François Papon
>>>>> fpa...@apache.org
>>>>>
>>>>> Le 14/12/2018 à 18:03, Claus Ibsen a écrit :
>>>>>> Hi
>>>>>>
>>>>>> Yay its good to see progress on this, and that we can easily have a
>>>>>> sneak-peak by browsing that staging site.
>>>>>>
>>>>>> Great work guys, love to see the collaboration going on, to
>>>>>> reinvigorate the Camel project and its website.
>>>>>>
>>>>>>
>>>>>> On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart 
>>>> wrote:
>>>>>>> Hi Cameleers,
>>>>>>> the first iteration of the build[1] of the new website is up on the
>>>> staging URL:
>>>>>>> https://camel.apache.org/staging/
>>>>>>>
>>>>>>> it took a while to get all the kinks worked out but it seems OK now.
>>>>>>>
>>>>>>> Bare in mind that this is still very early, rough version: links will
>>>>>>> be broken or point to wrong places, layout and styling is almost
>>>>>>> non-existant.
>>>>>>>
>>>>>>> This at least gives us the opportunity to see any changes we make
>>>>>>> really quickly online.
>>>>>>>
>>>>>>> I'll work on adding some READMEs to explain how to contribute and
>>>>>>> cleanup JIRA issues around the new website next.
>>>>>>>
>>>>>>> zoran
>>>>>>>
>>>>>>> [1]
>>>> https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity
>>>>>>> --
>>>>>>> Zoran Regvart
>>>> --
>>>> Zoran Regvart
>>>>
>
>


Re: Camel website

2018-12-17 Thread Francois Papon
Hi,

Thanks for your feeback!

For the mobile responsive, I didn't work on it yet but I keep it in mind ;)

Regards,

François Papon
fpa...@apache.org

Le 17/12/2018 à 12:41, Andrea Cosentino a écrit :
> Really nice! Only that problem on mobile, but it looks great.
>
> --
> Andrea Cosentino 
> --
> Apache Camel PMC Chair
> Apache Karaf Committer
> Apache Servicemix PMC Member
> Email: ancosen1...@yahoo.com
> Twitter: @oscerd2
> Github: oscerd
>
>
>
>
>
>
> On Monday, December 17, 2018, 9:33:21 AM GMT+1, Onder SEZGIN 
>  wrote: 
>
>
>
>
>
> Thanks François. It looks very nice.
> One minor comment:
> Look and feel is overlapping on mobile view. Maybe it could be adjusted to
> be more responsive.
>
> On Sun, Dec 16, 2018 at 3:59 PM Zoran Regvart  wrote:
>
>> Hi François,
>> I think that's awesome! Please do create a PR :)
>>
>> zoran
>> On Sat, Dec 15, 2018 at 7:28 PM Francois Papon
>>  wrote:
>>> Hi guys,
>>>
>>> I made some design integration on the website based on the new logo,
>>> it's not fully finished and it's just a proposal.
>>>
>>> You can have a preview about the home page here :
>>>
>>> https://openobject.fr/camel/
>>>
>>> If you like it I'm ready to push my PR and move forward with the
>>> documentation theme ;)
>>>
>>> Regards,
>>>
>>> François Papon
>>> fpa...@apache.org
>>>
>>> Le 14/12/2018 à 18:03, Claus Ibsen a écrit :
>>>> Hi
>>>>
>>>> Yay its good to see progress on this, and that we can easily have a
>>>> sneak-peak by browsing that staging site.
>>>>
>>>> Great work guys, love to see the collaboration going on, to
>>>> reinvigorate the Camel project and its website.
>>>>
>>>>
>>>> On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart 
>> wrote:
>>>>> Hi Cameleers,
>>>>> the first iteration of the build[1] of the new website is up on the
>> staging URL:
>>>>> https://camel.apache.org/staging/
>>>>>
>>>>> it took a while to get all the kinks worked out but it seems OK now.
>>>>>
>>>>> Bare in mind that this is still very early, rough version: links will
>>>>> be broken or point to wrong places, layout and styling is almost
>>>>> non-existant.
>>>>>
>>>>> This at least gives us the opportunity to see any changes we make
>>>>> really quickly online.
>>>>>
>>>>> I'll work on adding some READMEs to explain how to contribute and
>>>>> cleanup JIRA issues around the new website next.
>>>>>
>>>>> zoran
>>>>>
>>>>> [1]
>> https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity
>>>>> --
>>>>> Zoran Regvart
>>>>
>>
>> --
>> Zoran Regvart
>>


Re: Camel website

2018-12-15 Thread Francois Papon
Hi guys,

I made some design integration on the website based on the new logo,
it's not fully finished and it's just a proposal.

You can have a preview about the home page here :

https://openobject.fr/camel/

If you like it I'm ready to push my PR and move forward with the
documentation theme ;)

Regards,

François Papon
fpa...@apache.org

Le 14/12/2018 à 18:03, Claus Ibsen a écrit :
> Hi
>
> Yay its good to see progress on this, and that we can easily have a
> sneak-peak by browsing that staging site.
>
> Great work guys, love to see the collaboration going on, to
> reinvigorate the Camel project and its website.
>
>
> On Thu, Dec 13, 2018 at 12:36 PM Zoran Regvart  wrote:
>> Hi Cameleers,
>> the first iteration of the build[1] of the new website is up on the staging 
>> URL:
>>
>> https://camel.apache.org/staging/
>>
>> it took a while to get all the kinks worked out but it seems OK now.
>>
>> Bare in mind that this is still very early, rough version: links will
>> be broken or point to wrong places, layout and styling is almost
>> non-existant.
>>
>> This at least gives us the opportunity to see any changes we make
>> really quickly online.
>>
>> I'll work on adding some READMEs to explain how to contribute and
>> cleanup JIRA issues around the new website next.
>>
>> zoran
>>
>> [1] 
>> https://builds.apache.org/blue/organizations/jenkins/Camel.website/activity
>> --
>> Zoran Regvart
>
>



Re: Camel website

2018-12-12 Thread Francois Papon
Thanks!

Regards,

François Papon
fpa...@apache.org

Le 12/12/2018 à 16:12, Zoran Regvart a écrit :
> Hi Francois,
> yes, and with the separate build we can get much faster turnaround on
> the website, I'm just about to push these changes to git and I'll work
> on the build next.
>
> I've pushed Antora based directory changes to the `camel` git
> repository's `website` branch[1] few minutes ago.
>
> I'll work on the build next, and after that adding more information to
> README files to help with getting started locally on this,
>
> zoran
>
> [1] 
> https://github.com/apache/camel/commit/e5523701ca10458cc21f82bc0933f97009f8438f
> On Wed, Dec 12, 2018 at 1:02 PM Francois Papon
>  wrote:
>> Hi,
>>
>> Good point for the camel-website repository :)
>>
>> May be it could be interesting to have 2 jobs on Jenkins for the
>> website: master and PR. This jobs could build and published on online
>> demo site.
>>
>> Thoughts ?
>>
>> Regards,
>>
>> François Papon
>> fpa...@apache.org
>>
>> Le 12/12/2018 à 15:10, Zoran Regvart a écrit :
>>> Hi Cameleers,
>>> I've found some time to work on the website and here's the current
>>> status on the progress we made.
>>>
>>> We had some great contributions on the new website raging from the
>>> Asciidoctor theme and build for the user manual that Francois
>>> contributed, to the wiki pages migration that Alex, Andrea, Claus,
>>> Gregor, Pascal, Önder, Satyajit, Tadayoshi and Willem did (I'm sorry
>>> if I'm forgetting anyone).
>>>
>>> This started as an effort on the `website` branch where I tried to
>>> create a static build of the website using Hugo, a custom-built
>>> wrapper for Asciidoctor and a bunch of Gulp+Webpack tasks to tie it
>>> all together. That resulted in complex, slow to build and, obviously,
>>> for anyone besides me hard to contribute and comprehend ball of mud.
>>>
>>> I'm going to abandon that effort, and in turn focus on a (I think)
>>> simpler approach.
>>>
>>> The new approach is already looking (to me) much better in terms of
>>> simplicity and maintanability, and I'm about to polish it a bit and
>>> push it so that anyone can take a look and comment on it.
>>>
>>> I've focused on a Antora[1] based website build for the User manual
>>> and the Component reference -- this has great benefits of having
>>> support for documentation version out of the box. This way we can have
>>> the component reference built from different Camel versions (release
>>> branches).
>>>
>>> It is not without (some, I'd argue small) complexity, I needed to move
>>> files comprising the user manual and I've created a Gulp build that'll
>>> create directory structure Antora expects by creating symlinks from
>>> this directory structure to `component/camel-*/src/main/doc/*.adoc`.
>>> The end result is that we'll have symbolic links in the git
>>> repository, not sure if that's controversial, but it could be
>>> surprising for some. We could also move the component documentation
>>> from component Maven modules into a single Antora directory structure
>>> and that's something we can evaluate as well.
>>>
>>> Next, I've build an Antora theme, basically by forking the default
>>> theme and adding fonts and text styling that Francois created for the
>>> ASF Asciidoctor theme. This part still needs a lot of work to make it
>>> look much nicer.
>>>
>>> I'm now in the process of combining Hugo for the content besides the
>>> documentation, like main page, release notes, blog/news.
>>>
>>> Another thing is that I'll be moving the website from the camel git
>>> repository to the camel-website git repository, which will now contain
>>> the build scripts, all content besides the user manual and the
>>> component documentation and the Antora theme.
>>>
>>> I think I'll start merging to the master from the website branch as
>>> soon as the the work stabilizes a bit to help with the visibility of
>>> this work and to make it easier for other contributors to make
>>> changes.
>>>
>>> I would like to say that I think we're getting close to the new
>>> website with this new approach, and as always I very much welcome any
>>> comment or any other contribution in this effort. I'll be cleaning up
>>> the JIRA issue[2] and adding more tasks for anyone to pick up.
>>>
>>> Nothing is set in stone if anyone has a better idea of going about
>>> this feel free to comment :)
>>>
>>> I'll be posting updates on this thread as I progress on this, my goal
>>> is to have a rough version of the website (by rough I mean, some links
>>> not working, very basic design and topology) done by Christmas.
>>>
>>> zoran
>>>
>>> [1] http://antora.org/
>>> [2] https://issues.apache.org/jira/browse/CAMEL-11492
>


Re: Camel website

2018-12-12 Thread Francois Papon
Hi,

Good point for the camel-website repository :)

May be it could be interesting to have 2 jobs on Jenkins for the
website: master and PR. This jobs could build and published on online
demo site.

Thoughts ?

Regards,

François Papon
fpa...@apache.org

Le 12/12/2018 à 15:10, Zoran Regvart a écrit :
> Hi Cameleers,
> I've found some time to work on the website and here's the current
> status on the progress we made.
>
> We had some great contributions on the new website raging from the
> Asciidoctor theme and build for the user manual that Francois
> contributed, to the wiki pages migration that Alex, Andrea, Claus,
> Gregor, Pascal, Önder, Satyajit, Tadayoshi and Willem did (I'm sorry
> if I'm forgetting anyone).
>
> This started as an effort on the `website` branch where I tried to
> create a static build of the website using Hugo, a custom-built
> wrapper for Asciidoctor and a bunch of Gulp+Webpack tasks to tie it
> all together. That resulted in complex, slow to build and, obviously,
> for anyone besides me hard to contribute and comprehend ball of mud.
>
> I'm going to abandon that effort, and in turn focus on a (I think)
> simpler approach.
>
> The new approach is already looking (to me) much better in terms of
> simplicity and maintanability, and I'm about to polish it a bit and
> push it so that anyone can take a look and comment on it.
>
> I've focused on a Antora[1] based website build for the User manual
> and the Component reference -- this has great benefits of having
> support for documentation version out of the box. This way we can have
> the component reference built from different Camel versions (release
> branches).
>
> It is not without (some, I'd argue small) complexity, I needed to move
> files comprising the user manual and I've created a Gulp build that'll
> create directory structure Antora expects by creating symlinks from
> this directory structure to `component/camel-*/src/main/doc/*.adoc`.
> The end result is that we'll have symbolic links in the git
> repository, not sure if that's controversial, but it could be
> surprising for some. We could also move the component documentation
> from component Maven modules into a single Antora directory structure
> and that's something we can evaluate as well.
>
> Next, I've build an Antora theme, basically by forking the default
> theme and adding fonts and text styling that Francois created for the
> ASF Asciidoctor theme. This part still needs a lot of work to make it
> look much nicer.
>
> I'm now in the process of combining Hugo for the content besides the
> documentation, like main page, release notes, blog/news.
>
> Another thing is that I'll be moving the website from the camel git
> repository to the camel-website git repository, which will now contain
> the build scripts, all content besides the user manual and the
> component documentation and the Antora theme.
>
> I think I'll start merging to the master from the website branch as
> soon as the the work stabilizes a bit to help with the visibility of
> this work and to make it easier for other contributors to make
> changes.
>
> I would like to say that I think we're getting close to the new
> website with this new approach, and as always I very much welcome any
> comment or any other contribution in this effort. I'll be cleaning up
> the JIRA issue[2] and adding more tasks for anyone to pick up.
>
> Nothing is set in stone if anyone has a better idea of going about
> this feel free to comment :)
>
> I'll be posting updates on this thread as I progress on this, my goal
> is to have a rough version of the website (by rough I mean, some links
> not working, very basic design and topology) done by Christmas.
>
> zoran
>
> [1] http://antora.org/
> [2] https://issues.apache.org/jira/browse/CAMEL-11492



Re: [HEADS UP] Work on Apache Camel 3 is beginning

2018-12-11 Thread Francois Papon
Hi,

I'm agree for the website and we could also add a new dedicated page
about Camel K ?

Btw, I'm ready to help working on the website ;)

Regards,

François Papon
fpa...@apache.org

Le 12/12/2018 à 06:57, Willem Jiang a écrit :
> Thanks for th Zoran, I think website is quite important for the user
> find the documents and solutions.
> We definitely could get some help from the community if we put it into
> the roadmap.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Dec 11, 2018 at 10:18 PM Zoran Regvart  wrote:
>> Hi Cameleers,
>> exciting times ahead indeed :)
>>
>> I'd like to put the new website and work around Java 11 compatibility
>> on the roadmap.
>>
>> I had a couple of days to experiment with Antora for the user manual
>> and component documentation and thus far it seems very promising. Once
>> I merry this with the Hugo static site generator for the rest of the
>> pages we'll have a rough first pass of the new website (hope on doing
>> that soon). We've had a great deal of interest in getting this done
>> and few folks already helped or announced their willingness to help.
>> And I'm not saying that the website will be done for Camel 3 release,
>> I'd actually like to see it done in the next 1-2 months.
>>
>> For the Java 11 support, I think this should go in to the 2.x with our
>> current approach of testing on Java 11 and upgrading component
>> dependencies when they're Java 11 ready. All work on this is in the
>> `java-10-test` branch. One thought I had is that we could introduce a
>> `camel-java11-compat` dependency that would bring in the JEE APIs
>> (JAXB and the rest) that were removed from Java 11. For Camel 3,
>> perhaps we can make Java 11 the base minimum version -- would be good
>> to get some feedback on this. One more thing we could try to evaluate
>> is the use of Java modules, Camel 3, IMHO, should at least be Java
>> module ready, i.e. have `Automatic-Module-Name` in the manifest.
>> Perhaps we can count the number of component dependencies that are
>> usable on the module path and see if we can go ahead and add
>> `module-info.java` in (some?) of the components.
>>
>> zoran
>> On Tue, Dec 11, 2018 at 2:59 PM Andrea Cosentino
>>  wrote:
>>> Hello Camelers,
>>>
>>> We are starting the work on Apache Camel 3. We are working at multiple 
>>> levels to improve Camel and introduce new features.
>>>
>>> The first work has actually started by Guillaume Nodet in the start of 
>>> October, where he jump started by cleaning up the codebase, removed 
>>> deprecated code and components, improving the routing engine and other 
>>> internals in the core. His work is published on the sandbox/3.x branch. We 
>>> plan to use his work as the baseline for the actual Camel 3. I have helped 
>>> by aligning this branch with all the changes from the master branch (2.x) 
>>> so its fully up to date. The intention is to switch over the sandbox/3.x 
>>> branch as the new master branch, so we can start working on that branch and 
>>> being able to add new features, components etc. (as always) for Camel 3.
>>>
>>> For 2.x users we will create a 2.x branch where we plan to do 1 or 2 more 
>>> last 2.x releases, eg 2.24 and 2.25, before 3.0 is ready and released.
>>>
>>> Here in the beginning of the Camel 3 work is to continue the work from 
>>> Guillaume Nodet and finish up the cleanup of the codebase, modularize the 
>>> camel-core, etc.
>>>
>>> We invite community users and any Camel committers and developers who has 
>>> interest to help with the Camel 3 work. We have talked about doing a number 
>>> of milestone releases of 3.x that can help give feedback to us quicker and 
>>> faster. For example any Camel users of 2.x can try to upgrade and use the 
>>> 3.0 milestone releases to report back their findings.
>>>
>>> Over the coming weeks it would be good if we could work on the roadmap and 
>>> a rough timetable for Camel 3 so we can sketch out the first set of goals 
>>> for the first milestone release and then rinse and repeat for the upcoming 
>>> milestone releases.
>>>
>>> We have also talked about letting Camel 3 be a timeboxed release to avoid 
>>> it dragging out “forever”. It would be great if we can build and release 
>>> Camel 3 within 1 year of development, for example maybe try to aim for a 
>>> release in Q3 2019.
>>>
>>> We will keep the community posted on the progress, and as always we love 
>>> contribution and any feedback.
>>>
>>> Exciting times ahead!
>>>
>>> Thoughts?
>>>
>>> Claus & Andrea
>>>
>>> --
>>> Andrea Cosentino
>>> --
>>> Apache Camel PMC Chair
>>> Apache Karaf Committer
>>> Apache Servicemix PMC Member
>>> Email: ancosen1...@yahoo.com
>>> Twitter: @oscerd2
>>> Github: oscerd
>>
>>
>> --
>> Zoran Regvart


Re: ApacheCon 2019

2018-11-29 Thread Francois Papon
Yes it's sounds very good :)

regards,

François Papon
fpa...@apache.org

Le 29/11/2018 à 13:01, m...@bennet-schulz.de a écrit :
> +1
> Am 29. Nov. 2018, 08:35 +0100 schrieb Nicola Ferraro :
>> +1000
>>
>> Camel is one of the Apache's most successful projects and can't miss.
>>
>> I think we can fill an entire day. Just the part about camel k can fill at
>> least 3 slots and we've plenty of other topics.
>>
>> Nicola
>>
>>
>> Il giorno gio 29 nov 2018, 05:04 Jean-Baptiste Onofré  ha
>> scritto:
>>
>>> +1
>>>
>>> It sounds good to me. I also proposed half a day for Apache Karaf, so it
>>> makes sense for Camel.
>>>
>>> Regards
>>> JB
>>>
>>> On 29/11/2018 00:50, Zoran Regvart wrote:
 Hi Cameleers,
 there is a call for participation on private@ for ApacheCon 2019.
 Since this is 20 years of ASF and Camel has been around for more than
 a half of it I think it makes perfect sense/it's a good place to
 present/talk about Camel.

 So what do you think about having a Camel track at ApacheCon 2019 in
 Las Vegas? Do you feel like we can fill a half-day or a whole day of
 talks?

 I would like to see Camel represented there, as it's one of the
 biggest ASF projects very healthy and with a diverse community, and it
 seems really fitting to have at least half a day track or a full day
 track of talks/presentations around Camel.

 I would volunteer to be the chair for the track...

 zoran

>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>



Re: [VOTE] Release Apache Camel 2.23.0

2018-11-24 Thread Francois Papon
+1 (non-binding)

Thanks!

regards,

François Papon
fpa...@apache.org

Le 25/11/2018 à 00:26, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.23.0, a new minor release for
> the camel-2.23.x branch with 262 improvements and bug fixes. This is
> also the first release to support Spring Boot 2.1.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343345=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1114/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1114/org/apache/camel/apache-camel/2.23.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.23.0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.23.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.22.2

2018-11-02 Thread Francois Papon
+1 (non-binding)

Thanks for the release!

regards,

François Papon
fpa...@apache.org

Le 02/11/2018 à 10:23, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.2, a patch release for the
> camel-2.22.x branch with 37 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344006=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1113/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1113/org/apache/camel/apache-camel/2.22.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: Hosted web site

2018-10-31 Thread Francois Papon
Hi,

It's great, thanks Zoran!

I can take a look about the breaking CSS and links.

I'm sorry, I was very busy this month and I could not work on the website :(

It would be better now!

regards,

François Papon
fpa...@apache.org

Le 30/10/2018 à 17:04, Zoran Regvart a écrit :
> Hi Tadayoshi & Cameleers,
> so the staging site now works* it's at:
>
> https://camel.apache.org/staging/
>
> *and by that I mean: the content of camel-website's asf-site branch is
> published there. It is pretty much broken at the moment, CSS and links
> are generated with absolute values, I need to take a look and make
> them relative so that the website can be nested in that /staging
> directory.
>
> zoran
>
> On Tue, Oct 30, 2018 at 11:40 AM, Zoran Regvart  wrote:
>> Hi Tadayoshi,
>> I'm really sorry I had little time to look into this, the process
>> should look like this:
>>
>> We make changes on the camel.git gitbox repository (or GitHub mirror)
>> to the `website` branch (till it's merged over to `master`), Jenkins
>> builds the website (Jenkinsfile on `website` branch does this[1]) and
>> pushes to the camel-website.git repository's `asf-site` branch. Then a
>> script provided by the INFRA[2] should sync with the website's
>> /staging directory.
>>
>> I think we need a `asf-site-staging` and a `asf-site` branches on
>> `camel-website.git` repository and a way to merge from one repository
>> to the other (Jenkins job?), but let's make some smaller steps first.
>>
>> zoran
>>
>> [1] 
>> https://gitbox.apache.org/repos/asf?p=camel.git;a=blob;f=Jenkinsfile;h=f094a624332bed955c686ec4a9951aeaa004c258;hb=refs/heads/website#l47
>> [2] https://issues.apache.org/jira/browse/INFRA-15969
>>
>> On Tue, Oct 30, 2018 at 9:59 AM, Tadayoshi Sato
>>  wrote:
>>> Hi all,
>>>
>>> I've been working on migrating docs, and while there are still a number of
>>> pages to be migrated yet it's also becoming in good shape. I think it's
>>> good time to host the docs somewhere so that everyone can read and further
>>> contribute to the site.
>>>
>>> I'm aware that recently Francois and Zoran worked on doc site generation
>>> and https://github.com/apache/camel-website. Is it currently accessible
>>> online?  Can we publish the static site somewhere like GH Pages, surge.sh,
>>> or Netlify?
>>>
>>> The docs are already available on GH as asciidoc but the problem is that
>>> links of reference style i.e. <> do not work on the
>>> plain GH. I believe we need some place where those reference style links
>>> are also rendered.
>>>
>>> Best regards,
>>> Tadayoshi
>>
>>
>> --
>> Zoran Regvart
>
>



Re: [HEADS UP] Camel K is here!

2018-10-16 Thread Francois Papon
Congratulations!

This is an amazing work!

regards,

François Papon
fpa...@apache.org

Le 17/10/2018 à 02:24, Nicola Ferraro a écrit :
> Hi folks,
> after some months of brainstorming with the community and a bit more than
> one month of development, our Camel K project has reached a good level of
> stability and I've published the first blog post about it yesterday.
>
> For those of you who haven't heard of Camel K, it's now a subproject of
> Apache Camel (https://github.com/apache/camel-k) with the target of
> building a lightweight runtime for running integration code directly on
> cloud platforms like Kubernetes and Openshift. It was inspired by
> "serverless" principles and it will also target Knative shortly.
>
> With the exception of the runtime code, that remains the good old Camel
> Java framework with 200+ components and full of EIPs, most of the
> "operator" code in Camel K is written in Go. But the new language has not
> stopped many adventurer Camel developers that have actively contributed to
> the project during last month. We still have a long way in front of us,
> let's continue to make Camel great!
>
> So, please.. check the project out! Spread it to the world!
> And provide your feedback, so we can make it always better. We love any
> kind of contribution!
>
> Links follow..
>
> Announcement: https://twitter.com/ni_ferraro/status/1051872786946363392
> Article: https://www.nicolaferraro.me/2018/10/15/introducing-camel-k/
> Home: https://github.com/apache/camel-k
>
> Nicola
>



Re: [DOC] - generator

2018-09-27 Thread Francois Papon
Great :)

I will take a look on the issue and make some proposal ;)

regards,

François Papon
fpa...@apache.org

Le 27/09/2018 à 12:19, Zoran Regvart a écrit :
> Hi François,
> we have a issue[1] in JIRA with subtasks, feel free to work on,
> comment or create new issues pertaining the new website there.
>
> And nothing is set in stone, feel free to prototype, experiment...
>
> For myself, I'm having second thoughts about the use of Hugo because
> of the issues it causes around invoking asciidoctor to render
> asciidoc...
>
> zoran
>
> [1] https://issues.apache.org/jira/browse/CAMEL-11492
> On Wed, Sep 26, 2018 at 7:00 PM Francois Papon
>  wrote:
>> Thank you Zoran,
>>
>> Let me know how can I continue helping on the website and documentation :)
>>
>> regards,
>>
>> François Papon
>> fpa...@apache.org
>>
>> Le 26/09/2018 à 16:04, Zoran Regvart a écrit :
>>> Hi François,
>>> looks really good, I'll let Jean-Baptiste have a look before I merge.
>>> I've rendered the HTML and the PDF document locally, I think this only
>>> needs a tie in to the website build (I can take care of that) and
>>> we're good to go.
>>>
>>> I really like all the effort you put in making it look professional
>>> and styled with ASF brand, thank you :)
>>>
>>> zoran
>>> On Wed, Sep 26, 2018 at 1:43 PM Francois Papon
>>>  wrote:
>>>> Hi Zoran,
>>>>
>>>> I pushed a PR for a discussion around the generation.
>>>>
>>>> I added some guide about how to generate the HTML and PDF in the
>>>> comments of the PR.
>>>>
>>>> I would have some feedbacks before go forward on this :)
>>>>
>>>> regards,
>>>>
>>>> François Papon
>>>> fpa...@apache.org
>>>>
>>>> Le 25/09/2018 à 12:39, Zoran Regvart a écrit :
>>>>> Hi François,
>>>>> thank you for offering to help! Perhaps you can take a look at the
>>>>> asciidocs for the user manual we have in `docs/user-manual` and see if
>>>>> the this approach can be used to generate HTML and PDF from that.
>>>>>
>>>>> We're working on the new website in the `website` branch (I've just
>>>>> rebased it), there is a build job[1] that gets triggered when you make
>>>>> changes to that branch and pushes the resulting static files to
>>>>> `asf-site` branch of the `camel-webiste` subproject[2].
>>>>>
>>>>> For starters perhaps it would be nice to just have `/manual` on the
>>>>> new website with the generated HTML files.
>>>>>
>>>>> Please ping me with any questions, and feel free to change things
>>>>> around this is all work in progress
>>>>>
>>>>> zoran
>>>>>
>>>>> [1] 
>>>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/website/
>>>>> [2] https://github.com/apache/camel-website/tree/asf-site
>>>>>
>>>>> On Tue, Sep 25, 2018 at 5:08 AM Francois Papon
>>>>>  wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I know there is an actual effort on the manual and documentation of the
>>>>>> project and I would like to know if I can help on some items ?
>>>>>>
>>>>>> I made templates wich use the Apache website theme for generation of
>>>>>> HTML and PDF from asciidoc files and using the asciidoc-maven-plugin.
>>>>>>
>>>>>> If you are interested, you can take a look here :
>>>>>>
>>>>>> https://github.com/fpapon/apache-manual
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> --
>>>>>> François Papon
>>>>>> fpa...@apache.org
>>>>>>
>




Re: [DOC] - generator

2018-09-26 Thread Francois Papon
Thank you Zoran,

Let me know how can I continue helping on the website and documentation :)

regards,

François Papon
fpa...@apache.org

Le 26/09/2018 à 16:04, Zoran Regvart a écrit :
> Hi François,
> looks really good, I'll let Jean-Baptiste have a look before I merge.
> I've rendered the HTML and the PDF document locally, I think this only
> needs a tie in to the website build (I can take care of that) and
> we're good to go.
>
> I really like all the effort you put in making it look professional
> and styled with ASF brand, thank you :)
>
> zoran
> On Wed, Sep 26, 2018 at 1:43 PM Francois Papon
>  wrote:
>> Hi Zoran,
>>
>> I pushed a PR for a discussion around the generation.
>>
>> I added some guide about how to generate the HTML and PDF in the
>> comments of the PR.
>>
>> I would have some feedbacks before go forward on this :)
>>
>> regards,
>>
>> François Papon
>> fpa...@apache.org
>>
>> Le 25/09/2018 à 12:39, Zoran Regvart a écrit :
>>> Hi François,
>>> thank you for offering to help! Perhaps you can take a look at the
>>> asciidocs for the user manual we have in `docs/user-manual` and see if
>>> the this approach can be used to generate HTML and PDF from that.
>>>
>>> We're working on the new website in the `website` branch (I've just
>>> rebased it), there is a build job[1] that gets triggered when you make
>>> changes to that branch and pushes the resulting static files to
>>> `asf-site` branch of the `camel-webiste` subproject[2].
>>>
>>> For starters perhaps it would be nice to just have `/manual` on the
>>> new website with the generated HTML files.
>>>
>>> Please ping me with any questions, and feel free to change things
>>> around this is all work in progress
>>>
>>> zoran
>>>
>>> [1] 
>>> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/website/
>>> [2] https://github.com/apache/camel-website/tree/asf-site
>>>
>>> On Tue, Sep 25, 2018 at 5:08 AM Francois Papon
>>>  wrote:
>>>> Hi,
>>>>
>>>> I know there is an actual effort on the manual and documentation of the
>>>> project and I would like to know if I can help on some items ?
>>>>
>>>> I made templates wich use the Apache website theme for generation of
>>>> HTML and PDF from asciidoc files and using the asciidoc-maven-plugin.
>>>>
>>>> If you are interested, you can take a look here :
>>>>
>>>> https://github.com/fpapon/apache-manual
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> François Papon
>>>> fpa...@apache.org
>>>>
>>
>



Re: [DOC] - generator

2018-09-26 Thread Francois Papon
Hi Zoran,

I pushed a PR for a discussion around the generation.

I added some guide about how to generate the HTML and PDF in the
comments of the PR.

I would have some feedbacks before go forward on this :)

regards,

François Papon
fpa...@apache.org

Le 25/09/2018 à 12:39, Zoran Regvart a écrit :
> Hi François,
> thank you for offering to help! Perhaps you can take a look at the
> asciidocs for the user manual we have in `docs/user-manual` and see if
> the this approach can be used to generate HTML and PDF from that.
>
> We're working on the new website in the `website` branch (I've just
> rebased it), there is a build job[1] that gets triggered when you make
> changes to that branch and pushes the resulting static files to
> `asf-site` branch of the `camel-webiste` subproject[2].
>
> For starters perhaps it would be nice to just have `/manual` on the
> new website with the generated HTML files.
>
> Please ping me with any questions, and feel free to change things
> around this is all work in progress
>
> zoran
>
> [1] 
> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/website/
> [2] https://github.com/apache/camel-website/tree/asf-site
>
> On Tue, Sep 25, 2018 at 5:08 AM Francois Papon
>  wrote:
>> Hi,
>>
>> I know there is an actual effort on the manual and documentation of the
>> project and I would like to know if I can help on some items ?
>>
>> I made templates wich use the Apache website theme for generation of
>> HTML and PDF from asciidoc files and using the asciidoc-maven-plugin.
>>
>> If you are interested, you can take a look here :
>>
>> https://github.com/fpapon/apache-manual
>>
>> Regards,
>>
>> --
>> François Papon
>> fpa...@apache.org
>>
>




Re: [DOC] - generator

2018-09-25 Thread Francois Papon
Hi Zoran,

Thanks, I will check for having a '/manual' with HTML files.

For the generation, I already use it for the Apache Unomi project, you
can have a preview here :

  * HTML : https://unomi.incubator.apache.org/manual/latest/index.html
  * PDF :

https://dist.apache.org/repos/dist/release/incubator/unomi/1.3.0-incubating/unomi-manual-1_3_x.pdf

For the ping, you prefer IRC or Slack channel ?

Regards,

François Papon
fpa...@apache.org

Le 25/09/2018 à 12:39, Zoran Regvart a écrit :
> Hi François,
> thank you for offering to help! Perhaps you can take a look at the
> asciidocs for the user manual we have in `docs/user-manual` and see if
> the this approach can be used to generate HTML and PDF from that.
>
> We're working on the new website in the `website` branch (I've just
> rebased it), there is a build job[1] that gets triggered when you make
> changes to that branch and pushes the resulting static files to
> `asf-site` branch of the `camel-webiste` subproject[2].
>
> For starters perhaps it would be nice to just have `/manual` on the
> new website with the generated HTML files.
>
> Please ping me with any questions, and feel free to change things
> around this is all work in progress
>
> zoran
>
> [1] 
> https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel/job/website/
> [2] https://github.com/apache/camel-website/tree/asf-site
>
> On Tue, Sep 25, 2018 at 5:08 AM Francois Papon
>  wrote:
>> Hi,
>>
>> I know there is an actual effort on the manual and documentation of the
>> project and I would like to know if I can help on some items ?
>>
>> I made templates wich use the Apache website theme for generation of
>> HTML and PDF from asciidoc files and using the asciidoc-maven-plugin.
>>
>> If you are interested, you can take a look here :
>>
>> https://github.com/fpapon/apache-manual
>>
>> Regards,
>>
>> --
>> François Papon
>> fpa...@apache.org
>>
>



[DOC] - generator

2018-09-24 Thread Francois Papon
Hi,

I know there is an actual effort on the manual and documentation of the
project and I would like to know if I can help on some items ?

I made templates wich use the Apache website theme for generation of
HTML and PDF from asciidoc files and using the asciidoc-maven-plugin.

If you are interested, you can take a look here :

https://github.com/fpapon/apache-manual

Regards,

-- 
François Papon
fpa...@apache.org



Re: [VOTE] Release Apache Camel 2.22.1

2018-09-02 Thread Francois Papon
+1 (non-binding)

Thanks for the release !

regards,

François Papon
fpa...@apache.org

Le 02/09/2018 à 16:48, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.22.1, the first patch release
> for the camel-2.22.x branch with 47 improvements and bug fixes.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343346=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-/org/apache/camel/apache-camel/2.22.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.22.1
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.22.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.20.4

2018-07-21 Thread Francois Papon
+1 (non-binding)

Thanks !

François

François Papon
fpa...@apache.org

Le 21/07/2018 à 20:33, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote for releasing Apache Camel 2.20.4, the last planned new
> patch release for the camel-2.20.x branch.  This release includes 30
> fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342958=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1110/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1110/org/apache/camel/apache-camel/2.20.4/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.20.4
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.20.4
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.21.2

2018-07-17 Thread Francois Papon
+1 (non-binding)

Thanks !

regards,

François Papon
fpa...@apache.org
Yupiik - https://www.yupiik.com

Le 18/07/2018 à 01:46, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.2, the second patch
> release for the camel-2.21.x branch.  This release includes 49 fixes
> and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343107=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1109/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1109/org/apache/camel/apache-camel/2.21.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-2.21.2
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.21.1

2018-05-01 Thread Francois Papon
+1 (non-binding)

Thanks,

François


Le 29/04/2018 à 20:23, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.1, the first patch release
> for the camel-2.21.x branch.  This release includes 52 fixes and
> improvements that have been implemented since the initial release of
> Camel 2.21.0 about six weeks ago.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342869=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1106/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1106/org/apache/camel/apache-camel/2.21.1/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=commit;h=dedf656c7526ab6189519f0733e25ed3fed369f7
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.1
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.20.3

2018-03-26 Thread Francois Papon
+1 (non-binding)

Thanks for the release !

François


Le 26/03/2018 à 13:46, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.20.3, a new patch release for
> branch camel-2.20.x.  This release includes 33 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342652=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1105/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1105/org/apache/camel/apache-camel/2.20.3/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=commit;h=32bfda73ddd1ea8576bcb53dac496af9e0825f1a
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.20.3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.19.5

2018-03-25 Thread Francois Papon
+1 (non-binding)

Thanks !

François


Le 25/03/2018 à 11:59, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.19.5, the last planned patch
> release for branch camel-2.19.x.  This release includes 42 fixes and
> improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342135=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1104/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1104/org/apache/camel/apache-camel/2.19.5/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=commit;h=9bb653a479306ff8354fc16746adc029222a49b0
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.19.5
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.21.0

2018-03-12 Thread Francois Papon
+1 (non-binding)

Thanks for the release !

François


Le 11/03/2018 à 21:47, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.21.0, a new minor release
> with 400 new features, improvements and bug fixes.  A summary of the
> changes is available in the Camel wiki:
> https://cwiki.apache.org/confluence/display/CAMEL/Camel+2.21.0+Release.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341576=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1103/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1103/org/apache/camel/apache-camel/2.21.0/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=4a46f8170c70abbdb76485c6cabe5091cc70e838
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.21.0
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> As with every new minor version, this release introduces many changes
> and improvements. It would be great if we could get as much testing as
> possible for this release candidate.
>
> Thanks,
> Gregor



Re: [VOTE] Release Apache Camel 2.20.2

2018-01-23 Thread Francois Papon
+1 (non-binding)

Thanks for the release !

François


Le 23/01/2018 à 10:04, Gregor Zurowski a écrit :
> Hi Everyone:
>
> This is a vote to release Apache Camel 2.20.2, a new patch release for
> the 2.20.x branch that includes 41 fixes and improvements.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342152=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1102/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1102/org/apache/camel/apache-camel/2.20.2/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=commit;h=2a3310822da3f1992083e206b68af3172fcd3792
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 2.20.2
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor



Re: Elasticsearch5 components and Elasticsearch 6.x

2017-12-19 Thread Francois Papon
Hi,

As a Camel user, I agree about rename this component without version
number because actually we have to change camel route endpoint to
upgrade ES component.

+1

François


Le 19/12/2017 à 19:30, Zoran Regvart a écrit :
> Sounds very reasonable to me we should name it so it doesn't look outdated.
>
> We already had a couple of component renames in 2.20 (CAMEL-11242 and
> CAMEL-11575 come to mind) and there hasn't been any uproar from the
> community.
>
> So +1
>
> zoran
>
> On Tue, Dec 19, 2017 at 2:42 PM, Andrea Cosentino
>  wrote:
>> Hello,
>> Currently we have two components: Elasticsearch5 that will be deprecated and 
>> Elasticsearch5Rest that will be the main component, since it will use the ES 
>> rest client, suggested from Elasticsearch community.
>> ES 6 is already released and we have also the bundles for that.
>> Do we need to change the name of Elasticsearch5Rest to ElasticsearchRest and 
>> upgrade to 6.x?
>> I believe this is something we should try to accomplish before 2.21.0 
>> release.
>> Thanks.
>> --Andrea Cosentino --Apache Camel PMC 
>> MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: 
>> ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
>
>