Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

[Andrea Cosentino]

Looks really promising. Great work.

Il giorno mar 4 giu 2019 alle ore 19:04 Beto Flores 
ha scritto:

> Hi all.
>
> I have been collecting some ideas about how the Any23 Data Format could
> look like and I have put them into a document. Could you please give it a
> look and give me your feedback .
>
>
> https://docs.google.com/document/d/1rVuRQCM6Ungr5YzLZlP3T8qhsgQvI9-Wd9DmyTdkpGU/edit?usp=sharing
>
> Also, I will be pushing my first changes into my fork [1] .
>
> [1] https://github.com/betoflowv93/camel/tree/CAMEL-9260
>
> Cheers,
> Roberto
>
> El lun., 27 de may. de 2019 a la(s) 12:08, Andrea Cosentino (
> anco...@gmail.com) escribió:
>
> > Yes, imo it's a good idea to discuss on dev mailing list. Your plan is ok
> > from my point of view.
> >
> > Il lun 27 mag 2019, 18:59 Beto Flores  ha
> scritto:
> >
> > > Hi all.
> > >
> > > The GSoC coding period has started so I am focusing on the
> implementation
> > > of the Any23 Dataformat.
> > >
> > > I think I should be working on the following subtasks:
> > >
> > > - create a new branch in my fork for the project (CAMEL-9260) from the
> > > master branch.
> > >
> > > - create a new maven module in the components section for the new
> > > dataformat (camel-any23).
> > >
> > > -Add Apache Any23 as a dependecy.
> > >
> > > - create a document which describes the specific parameteres and
> > behaivors
> > > to be implemented in the dataformat and a small class diagram with the
> > main
> > > classes to be created, in order to disscuss the design with my mentors.
> > >
> > > Please let me know if you have suggestions. Also I would like to know
> how
> > > should I get in touch with my mentors.
> > > So far Andrea Cosentino, Zoran Regvart and Willem Jiang have shown some
> > > interest in the project, is that ok for you if we keep the
> communication
> > on
> > > the Dev mailing list?.
> > >
> > >
> > > Regards,
> > > Roberto
> > >
> > >
> > > El mar., 14 de may. de 2019 a la(s) 12:41, Beto Flores (
> > > betoflow...@gmail.com) escribió:
> > >
> > > > Hi Willem.
> > > >
> > > > Thanks so much. It would be great if you can help me as my mentor.
> > > > Currently, I have been trying to work on some Jira issues in order to
> > > > understand better Camel. I have being trying to reproduce [1] and
> come
> > up
> > > > with a solution.
> > > >
> > > > Please let me know if you have further suggestions on how I can
> better
> > > > take adventage of the bonding period.
> > > >
> > > > Also, I would like to know how to get in touch with you for planning
> > the
> > > > project during the coding period.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/CAMEL-13483
> > > >
> > > > Best,
> > > > Roberto
> > > >
> > > >
> > > > El mar., 14 de may. de 2019 a la(s) 03:28, Willem Jiang (
> > > > willem.ji...@gmail.com) escribió:
> > > >
> > > >> It's great to hear that you proposal was accepted.
> > > >> Did you have chance to discuss the detail with your mentor?
> > > >> If you need to find a mentor I'd happy to help you.
> > > >>
> > > >> Willem Jiang
> > > >>
> > > >> Twitter: willemjiang
> > > >> Weibo: 姜宁willem
> > > >>
> > > >> On Tue, May 7, 2019 at 5:22 AM Beto Flores 
> > > wrote:
> > > >> >
> > > >> > Hi all.
> > > >> >
> > > >> > I have just received an email from the GSoC 2019 program and my
> > > proposal
> > > >> > have been accepted. Thanks so much you guys for all your support
> > > during
> > > >> the
> > > >> > application period and really hope that this summer will be
> > productive
> > > >> > working with the Apache Camel Community.
> > > >> >
> > > >> >  Please let me know if you have suggestions on how to get started
> in
> > > the
> > > >> > community and start working on my project.
> > > >> >
> > > >> > Best,
> > > >> > Roberto.
> > > >> >
> > > >> > -- Forwarded message -
> > > >> > De: Google Summer of Code 
> > > >> > Date: lun., 6 de may. de 2019 a la(s) 16:07
> > > >> > Subject: GSoC 2019: Congratulations, your proposal with The Apache
> > > >> Software
> > > >> > Foundation has been accepted!
> > > >> > To: 
> > > >> >
> > > >> >
> > > >> > [image: Google Summer of Code]
> > > >> >
> > > >> > Hi Roberto Flores,
> > > >> >
> > > >> > Your proposal CAMEL-9260 Dataformat Apache Any23
> > > >> > <
> > > >>
> > >
> >
> https://summerofcode.withgoogle.com/dashboard/student/proposal/5081445427576832/
> > > >> >
> > > >> > has been accepted!
> > > >> >
> > > >> > Welcome to GSoC 2019!
> > > >> >
> > > >> > We look forward to seeing the great things you will accomplish
> this
> > > >> summer
> > > >> > with The Apache Software Foundation.
> > > >> >
> > > >> > The next thing you need to do is read the Information for Accepted
> > > >> Students
> > > >> > <
> > > https://developers.google.com/open-source/gsoc/help/accepted-students
> >.
> > > >> It
> > > >> > contains important information you need to know about your
> > > >> participation in
> > > >> > GSoC 2019.
> > > >> >
> > > >> > You will receive another email in the next 

Re: Quarkus

[Tadayoshi Sato]

Hi folks,

I like Peter's idea on having a separate repository for camel-quarkus.

In addition to his point, I would add that Quarkus is a newly born, cutting
edge technology, which itself should evolve fast and likely may not keep
how it works now for long as we see in, say, Node.js community. Having a
separate repository should let us experiment fast as well and catch up with
the rapid evolution in Quarkus without touching the main Camel codebase.

On Tue, Jun 4, 2019 at 8:07 PM Peter Palaga  wrote:

> Hi,
>
> I am fully welcoming the initiative to donate the code of Camel Quarkus
> extensions that currently live in Quarkus git repository [1] to Apache
> Camel community. I believe that's where the code can attract much more
> interested developers and users.
>
> I recently ported a couple of Camel components to Quarkus [2][3] and I
> plan to port more in the future.
>
> I'd like to express my opinion on which git repository should be the
> final home for that code.
>
> As Luca mentioned, there are two options there:
>
> (a) Apache Camel’s main git repository [4] or
> (b) A new separate repository under Apache organization.
>
> I am clearly in favor of (b) and my reasons for that revolve around the
> fact that the Camel main repository currently has 824 Maven modules.
> That size has a number of negative impacts on developers day-to-day life:
>
> * It takes tens of minutes to build without tests and hours with tests.
> * Full test suite cannot be run on each pull request and broken master
> is a possible consequence
> * I was told it is practically not viable to import that big source tree
> into IntelliJ (I am not IntelliJ user). Given enough memory, Eclipse can
> now import the whole source tree in a reasonable time [5]. Anyway,
> working with it feels rather slow.
>
> Adding more modules to support Quarkus would make the situation even worse.
>
> Having a separate repo for the Camel Quarkus extensions would make the
> life easier for both folks working on the Camel side (smaller source
> tree) and on the camel-quarkus side (faster dev builds, faster CI, more
> control over the supported Camel version).
>
> I prepared a proof of concept how such a separate repository could look
> like: https://github.com/ppalaga/camel-quarkus
>
> For the bleeding edge development work the repo is using srcdeps [6][7]
> to manage non-released dependencies of Apache Camel and Quarkus. srcdeps
> allows for declaring dependencies in terms of git commit sha1s instead
> of versions present in remote Maven repositories.
>
> srcdeps is able to reduce the Maven module hierarchy of the dependency
> project to only those modules required by the current repository. Thanks
> to this, only 62 Camel modules need to be built to satisfy
> camel-quarkus. Building those 62 Camel modules takes about two and a
> half minutes on my laptop.
> I am listing various build times of the camel-quarkus repo in the readme
> [8]
>
>
> [1] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
> [2] https://github.com/quarkusio/quarkus/pull/2542
> [3] https://github.com/quarkusio/quarkus/pull/2361
> [4] https://github.com/apache/camel
> [5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668
> [6] https://github.com/srcdeps/srcdeps-maven
> [7] http://ppalaga.github.io/presentations/181011-jcon-duesseldorf
> [8] https://github.com/ppalaga/camel-quarkus#fast-build-times
>
> Thanks,
>
> Peter
> --
> Peter Palaga, Red Hat Fuse
>
> On 04/06/2019 12:44, Andrea Cosentino wrote:
> > +1 for working with the Quarkus community.
> >
> > I don't think this would be an incubator project btw, it should be a
> > subproject if it will go in a separate repo or it will be placed in the
> > main repo as a platform.
> >
> > We can discuss this later by the way.
> >
> >
> >
> > Il giorno mar 4 giu 2019 alle ore 12:34 Willem Jiang <
> willem.ji...@gmail.com>
> > ha scritto:
> >
> >> +1 for working with Quarkus to make the Camel Application more light and
> >> fast.
> >>
> >> For the code donation part, we need to go through the IP clearance
> >> process[1].
> >> Please let me know if you have any questions about this.
> >>
> >> [1]https://incubator.apache.org/ip-clearance/
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli 
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> In the past months some folks at Red Hat have been working on the
> >>> integration between Apache Camel and Quarkus. For those not familiar
> >>> with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
> >>> framework tailored for GraalVM and HotSpot that bring fast startup
> >>> and low memory footprint to Java based application by leverage clever
> >>> build time optimizations and AOT compilation through Substrate VM [1].
> >>>
> >>> The result of the experimentation is available in the Quarkus
> >>> repository [2][3] and I’m also working on an experimental branch
> >>> on Camel K [4] to bring Quarkus on the 

Re: [VOTE]

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

[Jason Brock]

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 giorno mar 30 apr 2019 alle ore 17:20 Jason Brock <
>> jbr...@redhat.com>
>> > > ha
>> > > > scritto:
>> > > >
>> > > >
>> > > > > So far we have
>> > > > >
>> > 

Re: GSoC 2019: Congratulations, your proposal with The Apache Software Foundation has been accepted!

[Beto Flores]

Hi all.

I have been collecting some ideas about how the Any23 Data Format could
look like and I have put them into a document. Could you please give it a
look and give me your feedback .

https://docs.google.com/document/d/1rVuRQCM6Ungr5YzLZlP3T8qhsgQvI9-Wd9DmyTdkpGU/edit?usp=sharing

Also, I will be pushing my first changes into my fork [1] .

[1] https://github.com/betoflowv93/camel/tree/CAMEL-9260

Cheers,
Roberto

El lun., 27 de may. de 2019 a la(s) 12:08, Andrea Cosentino (
anco...@gmail.com) escribió:

> Yes, imo it's a good idea to discuss on dev mailing list. Your plan is ok
> from my point of view.
>
> Il lun 27 mag 2019, 18:59 Beto Flores  ha scritto:
>
> > Hi all.
> >
> > The GSoC coding period has started so I am focusing on the implementation
> > of the Any23 Dataformat.
> >
> > I think I should be working on the following subtasks:
> >
> > - create a new branch in my fork for the project (CAMEL-9260) from the
> > master branch.
> >
> > - create a new maven module in the components section for the new
> > dataformat (camel-any23).
> >
> > -Add Apache Any23 as a dependecy.
> >
> > - create a document which describes the specific parameteres and
> behaivors
> > to be implemented in the dataformat and a small class diagram with the
> main
> > classes to be created, in order to disscuss the design with my mentors.
> >
> > Please let me know if you have suggestions. Also I would like to know how
> > should I get in touch with my mentors.
> > So far Andrea Cosentino, Zoran Regvart and Willem Jiang have shown some
> > interest in the project, is that ok for you if we keep the communication
> on
> > the Dev mailing list?.
> >
> >
> > Regards,
> > Roberto
> >
> >
> > El mar., 14 de may. de 2019 a la(s) 12:41, Beto Flores (
> > betoflow...@gmail.com) escribió:
> >
> > > Hi Willem.
> > >
> > > Thanks so much. It would be great if you can help me as my mentor.
> > > Currently, I have been trying to work on some Jira issues in order to
> > > understand better Camel. I have being trying to reproduce [1] and come
> up
> > > with a solution.
> > >
> > > Please let me know if you have further suggestions on how I can better
> > > take adventage of the bonding period.
> > >
> > > Also, I would like to know how to get in touch with you for planning
> the
> > > project during the coding period.
> > >
> > > [1] https://issues.apache.org/jira/browse/CAMEL-13483
> > >
> > > Best,
> > > Roberto
> > >
> > >
> > > El mar., 14 de may. de 2019 a la(s) 03:28, Willem Jiang (
> > > willem.ji...@gmail.com) escribió:
> > >
> > >> It's great to hear that you proposal was accepted.
> > >> Did you have chance to discuss the detail with your mentor?
> > >> If you need to find a mentor I'd happy to help you.
> > >>
> > >> Willem Jiang
> > >>
> > >> Twitter: willemjiang
> > >> Weibo: 姜宁willem
> > >>
> > >> On Tue, May 7, 2019 at 5:22 AM Beto Flores 
> > wrote:
> > >> >
> > >> > Hi all.
> > >> >
> > >> > I have just received an email from the GSoC 2019 program and my
> > proposal
> > >> > have been accepted. Thanks so much you guys for all your support
> > during
> > >> the
> > >> > application period and really hope that this summer will be
> productive
> > >> > working with the Apache Camel Community.
> > >> >
> > >> >  Please let me know if you have suggestions on how to get started in
> > the
> > >> > community and start working on my project.
> > >> >
> > >> > Best,
> > >> > Roberto.
> > >> >
> > >> > -- Forwarded message -
> > >> > De: Google Summer of Code 
> > >> > Date: lun., 6 de may. de 2019 a la(s) 16:07
> > >> > Subject: GSoC 2019: Congratulations, your proposal with The Apache
> > >> Software
> > >> > Foundation has been accepted!
> > >> > To: 
> > >> >
> > >> >
> > >> > [image: Google Summer of Code]
> > >> >
> > >> > Hi Roberto Flores,
> > >> >
> > >> > Your proposal CAMEL-9260 Dataformat Apache Any23
> > >> > <
> > >>
> >
> https://summerofcode.withgoogle.com/dashboard/student/proposal/5081445427576832/
> > >> >
> > >> > has been accepted!
> > >> >
> > >> > Welcome to GSoC 2019!
> > >> >
> > >> > We look forward to seeing the great things you will accomplish this
> > >> summer
> > >> > with The Apache Software Foundation.
> > >> >
> > >> > The next thing you need to do is read the Information for Accepted
> > >> Students
> > >> > <
> > https://developers.google.com/open-source/gsoc/help/accepted-students>.
> > >> It
> > >> > contains important information you need to know about your
> > >> participation in
> > >> > GSoC 2019.
> > >> >
> > >> > You will receive another email in the next few days with information
> > >> about
> > >> > your stipend.
> > >> >
> > >> > If you have any questions, please email the Google Summer of Code
> > >> support
> > >> > team at gsoc-supp...@google.com.
> > >> >
> > >> > Have a great summer!
> > >> >
> > >> > -*Google Summer of Code team*
> > >> >
> > >> > This email was sent to betoflow...@gmail.com.
> > >> >
> > >> > You are receiving this email because of your 

[GitHub] [camel-k] marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11

[GitBox]

marcredhat commented on issue #493: camel-k on Openshift Container Platform 3.11
URL: https://github.com/apache/camel-k/issues/493#issuecomment-498753237
 
 
   Hi @ShravanGeek, 
   
   You should find it on the master, please see 
https://docs.openshift.com/container-platform/3.11/install_config/master_node_configuration.html.
   
   Please create a new issue at https://github.com/apache/camel-k/issues.
   Feel free to link to this one as you see fit.
   
   Thanks,
   Marc


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] marcredhat closed issue #493: camel-k on Openshift Container Platform 3.11

[GitBox]

marcredhat closed issue #493: camel-k on Openshift Container Platform 3.11
URL: https://github.com/apache/camel-k/issues/493
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] nicolaferraro opened a new pull request #724: Filter allowed env variables in Knative

[GitBox]

nicolaferraro opened a new pull request #724: Filter allowed env variables in 
Knative
URL: https://github.com/apache/camel-k/pull/724
 
 
   Fix #722
   
   Some rules have been enforced in 0.6.0: 
https://github.com/knative/serving/blob/ce96dd74b1c85f024d63ce0991d4bf61aced582a/pkg/apis/serving/fieldmask.go#L311-L312


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Quarkus

[Andrea Cosentino]

My fault about the ip-clearance. We must pass through that step. Thanks for
pointing this out Willem. The incubator name deceived me.

Il mar 4 giu 2019, 12:44 Andrea Cosentino  ha scritto:

> +1 for working with the Quarkus community.
>
> I don't think this would be an incubator project btw, it should be a
> subproject if it will go in a separate repo or it will be placed in the
> main repo as a platform.
>
> We can discuss this later by the way.
>
>
>
> Il giorno mar 4 giu 2019 alle ore 12:34 Willem Jiang <
> willem.ji...@gmail.com> ha scritto:
>
>> +1 for working with Quarkus to make the Camel Application more light and
>> fast.
>>
>> For the code donation part, we need to go through the IP clearance
>> process[1].
>> Please let me know if you have any questions about this.
>>
>> [1]https://incubator.apache.org/ip-clearance/
>>
>> Willem Jiang
>>
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>>
>> On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli 
>> wrote:
>> >
>> > Hi,
>> >
>> > In the past months some folks at Red Hat have been working on the
>> > integration between Apache Camel and Quarkus. For those not familiar
>> > with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
>> > framework tailored for GraalVM and HotSpot that bring fast startup
>> > and low memory footprint to Java based application by leverage clever
>> > build time optimizations and AOT compilation through Substrate VM [1].
>> >
>> > The result of the experimentation is available in the Quarkus
>> > repository [2][3] and I’m also working on an experimental branch
>> > on Camel K [4] to bring Quarkus on the K side based on my latest
>> > blog “Adventures in GraalVM: polyglot Camel (k) native routes
>> > with Quarkus”  [5]
>> >
>> > I do believe that both communities can benefit from a collaboration:
>> >
>> > Apache Camel can benefit from Quarkus to become
>> > a) Even more suitable for microservices
>> > b) Suitable for serverless workloads as Quarkus among others enables
>> >built-time warmup of the Camel Context, and elimination of dead-code
>> >(code that was only used during warmup) which is a key enabler for
>> >very fast start-up and low memory footprint Apache Camel can be on
>> >the innovative forefront with a cloud native Java stack for running
>> >modern serverless workloads on Kubernetes/Knative with Camel K and
>> >Camel Quarkus
>> >
>> > So I’m proposing to officially support Quarkus in Apache Camel’s main
>> > repository (or a dedicated one if it suits better) by creating a new
>> > platform along with those we support as today (Spring Boot, Karaf).
>> >
>> > Quarkus’ people is keen to donate the code related to Apache Camel
>> > hosted in theirs repository to the Apache Software foundation.
>> >
>> > There has been some other users in the community whom have tried
>> > Quarkus and Camel together and written blogs [6] about their experience,
>> > and Claus also posted a quick gif animation of native compiled Camel
>> > with Quarkus starting up in 7 milliseconds and taking up only 15mb
>> > of memory [7].
>> >
>> > Thoughts ?
>> >
>> > Luca
>> >
>> > [1] https://quarkus.io/
>> > [2] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
>> > [3]
>> https://github.com/quarkusio/quarkus-quickstarts/tree/master/camel-java
>> > [4]
>> >
>> https://github.com/lburgazzoli/apache-camel-k-runtime/tree/quarkus-runtime
>> > [5] https://bit.ly/2HvOrh0
>> > [6] https://bit.ly/2WDtCbW
>> > [7]
>> >
>> https://www.linkedin.com/feed/update/urn:li:activity:6521869236153970688/
>> >
>> > ---
>> > Luca Burgazzoli
>>
>

[GitHub] [camel-k] nicolaferraro opened a new pull request #723: [WIP]: automatically configure global build strategy

[GitBox]

nicolaferraro opened a new pull request #723: [WIP]: automatically configure 
global build strategy
URL: https://github.com/apache/camel-k/pull/723
 
 
   Fix #703
   
   This works on OpenShift. I'm checking Kubernetes.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] maschmid opened a new issue #722: examples/knative broken on OpenShift knative 0.6.0, must not set the field(s): spec.runLatest.configuration.revisionTemplate.spec.container.env[11]

[GitBox]

maschmid opened a new issue #722: examples/knative broken on OpenShift knative 
0.6.0, must not set the field(s): 
spec.runLatest.configuration.revisionTemplate.spec.container.env[11].valueFrom.fieldRef
URL: https://github.com/apache/camel-k/issues/722
 
 
   Attempting to run camelk 0.3.3 examples/knative demo on OpenShift 4.1.rc9 
with knative serving & eventing 0.6.0 (installed from operatorhub),
   
   fails with the following Reconciler error in the camel-k-operator
   
   ```
   
{"level":"info","ts":1559655631.553665,"logger":"camel-k.controller.integration","msg":"Reconciling
 Integration","request-namespace":"myproject","request-name":"printer"}
   
{"level":"info","ts":1559655631.5537536,"logger":"camel-k.controller.integration","msg":"Invoking
 action 
deploy","request-namespace":"myproject","request-name":"printer","api-version":"camel.apache.org/v1alpha1","kind":"Integration","ns":"myproject","name":"printer"}
   
{"level":"info","ts":1559655631.5538898,"logger":"camel-k.trait","msg":"Apply 
trait: camel"}
   {"level":"info","ts":1559655631.555041,"logger":"camel-k.trait","msg":"Apply 
trait: gc"}
   
{"level":"info","ts":1559655631.255,"logger":"camel-k.trait","msg":"Apply 
trait: knative"}
   
{"level":"info","ts":1559655631.818,"logger":"camel-k.trait","msg":"Apply 
trait: environment"}
   
{"level":"info","ts":1559655631.944,"logger":"camel-k.trait","msg":"Apply 
trait: deployer"}
   
{"level":"info","ts":1559655631.5559294,"logger":"camel-k.trait","msg":"Apply 
trait: knative-service"}
   
{"level":"info","ts":1559655631.5559826,"logger":"camel-k.trait","msg":"Apply 
trait: container"}
   
{"level":"info","ts":1559655631.5559938,"logger":"camel-k.trait","msg":"Apply 
trait: classpath"}
   
{"level":"info","ts":1559655631.5560288,"logger":"camel-k.trait","msg":"Apply 
trait: istio"}
   
{"level":"info","ts":1559655631.5560393,"logger":"camel-k.trait","msg":"Apply 
trait: owner"}
   
{"level":"error","ts":1559655631.5794945,"logger":"kubebuilder.controller","msg":"Reconciler
 
error","controller":"integration-controller","request":"myproject/printer","error":"could
 not create or replace resource printer: Internal error occurred: admission 
webhook \"webhook.serving.knative.dev\" denied the request: mutation failed: 
must not set the field(s): 
spec.runLatest.configuration.revisionTemplate.spec.container.env[11].valueFrom.fieldRef,
 
spec.runLatest.configuration.revisionTemplate.spec.container.env[12].valueFrom.fieldRef","errorVerbose":"Internal
 error occurred: admission webhook \"webhook.serving.knative.dev\" denied the 
request: mutation failed: must not set the field(s): 
spec.runLatest.configuration.revisionTemplate.spec.container.env[11].valueFrom.fieldRef,
 
spec.runLatest.configuration.revisionTemplate.spec.container.env[12].valueFrom.fieldRef\ncould
 not create or replace resource 

[GitHub] [camel-k] astefanutti merged pull request #713: Fix #707: sign released artifacts

[GitBox]

astefanutti merged pull request #713: Fix #707: sign released artifacts
URL: https://github.com/apache/camel-k/pull/713
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti closed issue #707: PGP Sign released artifacts

[GitBox]

astefanutti closed issue #707: PGP Sign released artifacts
URL: https://github.com/apache/camel-k/issues/707
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] oscerd commented on issue #713: Fix #707: sign released artifacts

[GitBox]

oscerd commented on issue #713: Fix #707: sign released artifacts
URL: https://github.com/apache/camel-k/pull/713#issuecomment-498646212
 
 
   I think this can be merged.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Quarkus

[Peter Palaga]

Hi,

I am fully welcoming the initiative to donate the code of Camel Quarkus 
extensions that currently live in Quarkus git repository [1] to Apache 
Camel community. I believe that's where the code can attract much more 
interested developers and users.


I recently ported a couple of Camel components to Quarkus [2][3] and I 
plan to port more in the future.


I'd like to express my opinion on which git repository should be the 
final home for that code.


As Luca mentioned, there are two options there:

(a) Apache Camel’s main git repository [4] or
(b) A new separate repository under Apache organization.

I am clearly in favor of (b) and my reasons for that revolve around the 
fact that the Camel main repository currently has 824 Maven modules. 
That size has a number of negative impacts on developers day-to-day life:


* It takes tens of minutes to build without tests and hours with tests.
* Full test suite cannot be run on each pull request and broken master 
is a possible consequence
* I was told it is practically not viable to import that big source tree 
into IntelliJ (I am not IntelliJ user). Given enough memory, Eclipse can 
now import the whole source tree in a reasonable time [5]. Anyway, 
working with it feels rather slow.


Adding more modules to support Quarkus would make the situation even worse.

Having a separate repo for the Camel Quarkus extensions would make the 
life easier for both folks working on the Camel side (smaller source 
tree) and on the camel-quarkus side (faster dev builds, faster CI, more 
control over the supported Camel version).


I prepared a proof of concept how such a separate repository could look 
like: https://github.com/ppalaga/camel-quarkus


For the bleeding edge development work the repo is using srcdeps [6][7] 
to manage non-released dependencies of Apache Camel and Quarkus. srcdeps 
allows for declaring dependencies in terms of git commit sha1s instead 
of versions present in remote Maven repositories.


srcdeps is able to reduce the Maven module hierarchy of the dependency 
project to only those modules required by the current repository. Thanks 
to this, only 62 Camel modules need to be built to satisfy 
camel-quarkus. Building those 62 Camel modules takes about two and a 
half minutes on my laptop.

I am listing various build times of the camel-quarkus repo in the readme [8]


[1] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
[2] https://github.com/quarkusio/quarkus/pull/2542
[3] https://github.com/quarkusio/quarkus/pull/2361
[4] https://github.com/apache/camel
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668
[6] https://github.com/srcdeps/srcdeps-maven
[7] http://ppalaga.github.io/presentations/181011-jcon-duesseldorf
[8] https://github.com/ppalaga/camel-quarkus#fast-build-times

Thanks,

Peter
--
Peter Palaga, Red Hat Fuse

On 04/06/2019 12:44, Andrea Cosentino wrote:

+1 for working with the Quarkus community.

I don't think this would be an incubator project btw, it should be a
subproject if it will go in a separate repo or it will be placed in the
main repo as a platform.

We can discuss this later by the way.



Il giorno mar 4 giu 2019 alle ore 12:34 Willem Jiang 
ha scritto:


+1 for working with Quarkus to make the Camel Application more light and
fast.

For the code donation part, we need to go through the IP clearance
process[1].
Please let me know if you have any questions about this.

[1]https://incubator.apache.org/ip-clearance/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli 
wrote:


Hi,

In the past months some folks at Red Hat have been working on the
integration between Apache Camel and Quarkus. For those not familiar
with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
framework tailored for GraalVM and HotSpot that bring fast startup
and low memory footprint to Java based application by leverage clever
build time optimizations and AOT compilation through Substrate VM [1].

The result of the experimentation is available in the Quarkus
repository [2][3] and I’m also working on an experimental branch
on Camel K [4] to bring Quarkus on the K side based on my latest
blog “Adventures in GraalVM: polyglot Camel (k) native routes
with Quarkus”  [5]

I do believe that both communities can benefit from a collaboration:

Apache Camel can benefit from Quarkus to become
a) Even more suitable for microservices
b) Suitable for serverless workloads as Quarkus among others enables
built-time warmup of the Camel Context, and elimination of dead-code
(code that was only used during warmup) which is a key enabler for
very fast start-up and low memory footprint Apache Camel can be on
the innovative forefront with a cloud native Java stack for running
modern serverless workloads on Kubernetes/Knative with Camel K and
Camel Quarkus

So I’m proposing to officially support Quarkus in Apache Camel’s main
repository (or a dedicated one if it 

[GitHub] [camel-k] ShravanGeek commented on issue #493: camel-k on Openshift Container Platform 3.11

[GitBox]

ShravanGeek commented on issue #493: camel-k on Openshift Container Platform 
3.11
URL: https://github.com/apache/camel-k/issues/493#issuecomment-498625408
 
 
   Hi @marcredhat I'm not able to find this file 
"/etc/origin/master/master-config.yaml" in my instance. I have installed 
openshift 3.11 on Ubuntu 18.04. Could you guide me on how to find that file? or 
is there any another option available to successfully run the camel-k? Thanks 
for your time.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] nicolaferraro commented on issue #683: Release 0.3.4

[GitBox]

nicolaferraro commented on issue #683: Release 0.3.4
URL: https://github.com/apache/camel-k/issues/683#issuecomment-498623762
 
 
   I've created a [milestone for 
0.3.4](https://github.com/apache/camel-k/milestone/2). Please add the issues 
you want to include. I'll cut a release once they're done.
   
   @lburgazzoli, @astefanutti, @jamesnetherton, @valdar, @oscerd 


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] nicolaferraro commented on issue #703: Automatically use pod build strategy in "AllNamespaces" setup

[GitBox]

nicolaferraro commented on issue #703: Automatically use pod build strategy in 
"AllNamespaces" setup
URL: https://github.com/apache/camel-k/issues/703#issuecomment-498622931
 
 
   I'd try to have a working version for next 0.3.4 release


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Quarkus

[Andrea Cosentino]

+1 for working with the Quarkus community.

I don't think this would be an incubator project btw, it should be a
subproject if it will go in a separate repo or it will be placed in the
main repo as a platform.

We can discuss this later by the way.



Il giorno mar 4 giu 2019 alle ore 12:34 Willem Jiang 
ha scritto:

> +1 for working with Quarkus to make the Camel Application more light and
> fast.
>
> For the code donation part, we need to go through the IP clearance
> process[1].
> Please let me know if you have any questions about this.
>
> [1]https://incubator.apache.org/ip-clearance/
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli 
> wrote:
> >
> > Hi,
> >
> > In the past months some folks at Red Hat have been working on the
> > integration between Apache Camel and Quarkus. For those not familiar
> > with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
> > framework tailored for GraalVM and HotSpot that bring fast startup
> > and low memory footprint to Java based application by leverage clever
> > build time optimizations and AOT compilation through Substrate VM [1].
> >
> > The result of the experimentation is available in the Quarkus
> > repository [2][3] and I’m also working on an experimental branch
> > on Camel K [4] to bring Quarkus on the K side based on my latest
> > blog “Adventures in GraalVM: polyglot Camel (k) native routes
> > with Quarkus”  [5]
> >
> > I do believe that both communities can benefit from a collaboration:
> >
> > Apache Camel can benefit from Quarkus to become
> > a) Even more suitable for microservices
> > b) Suitable for serverless workloads as Quarkus among others enables
> >built-time warmup of the Camel Context, and elimination of dead-code
> >(code that was only used during warmup) which is a key enabler for
> >very fast start-up and low memory footprint Apache Camel can be on
> >the innovative forefront with a cloud native Java stack for running
> >modern serverless workloads on Kubernetes/Knative with Camel K and
> >Camel Quarkus
> >
> > So I’m proposing to officially support Quarkus in Apache Camel’s main
> > repository (or a dedicated one if it suits better) by creating a new
> > platform along with those we support as today (Spring Boot, Karaf).
> >
> > Quarkus’ people is keen to donate the code related to Apache Camel
> > hosted in theirs repository to the Apache Software foundation.
> >
> > There has been some other users in the community whom have tried
> > Quarkus and Camel together and written blogs [6] about their experience,
> > and Claus also posted a quick gif animation of native compiled Camel
> > with Quarkus starting up in 7 milliseconds and taking up only 15mb
> > of memory [7].
> >
> > Thoughts ?
> >
> > Luca
> >
> > [1] https://quarkus.io/
> > [2] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
> > [3]
> https://github.com/quarkusio/quarkus-quickstarts/tree/master/camel-java
> > [4]
> >
> https://github.com/lburgazzoli/apache-camel-k-runtime/tree/quarkus-runtime
> > [5] https://bit.ly/2HvOrh0
> > [6] https://bit.ly/2WDtCbW
> > [7]
> >
> https://www.linkedin.com/feed/update/urn:li:activity:6521869236153970688/
> >
> > ---
> > Luca Burgazzoli
>

Re: Quarkus

[Willem Jiang]

+1 for working with Quarkus to make the Camel Application more light and fast.

For the code donation part, we need to go through the IP clearance process[1].
Please let me know if you have any questions about this.

[1]https://incubator.apache.org/ip-clearance/

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Jun 4, 2019 at 5:45 PM Luca Burgazzoli  wrote:
>
> Hi,
>
> In the past months some folks at Red Hat have been working on the
> integration between Apache Camel and Quarkus. For those not familiar
> with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
> framework tailored for GraalVM and HotSpot that bring fast startup
> and low memory footprint to Java based application by leverage clever
> build time optimizations and AOT compilation through Substrate VM [1].
>
> The result of the experimentation is available in the Quarkus
> repository [2][3] and I’m also working on an experimental branch
> on Camel K [4] to bring Quarkus on the K side based on my latest
> blog “Adventures in GraalVM: polyglot Camel (k) native routes
> with Quarkus”  [5]
>
> I do believe that both communities can benefit from a collaboration:
>
> Apache Camel can benefit from Quarkus to become
> a) Even more suitable for microservices
> b) Suitable for serverless workloads as Quarkus among others enables
>built-time warmup of the Camel Context, and elimination of dead-code
>(code that was only used during warmup) which is a key enabler for
>very fast start-up and low memory footprint Apache Camel can be on
>the innovative forefront with a cloud native Java stack for running
>modern serverless workloads on Kubernetes/Knative with Camel K and
>Camel Quarkus
>
> So I’m proposing to officially support Quarkus in Apache Camel’s main
> repository (or a dedicated one if it suits better) by creating a new
> platform along with those we support as today (Spring Boot, Karaf).
>
> Quarkus’ people is keen to donate the code related to Apache Camel
> hosted in theirs repository to the Apache Software foundation.
>
> There has been some other users in the community whom have tried
> Quarkus and Camel together and written blogs [6] about their experience,
> and Claus also posted a quick gif animation of native compiled Camel
> with Quarkus starting up in 7 milliseconds and taking up only 15mb
> of memory [7].
>
> Thoughts ?
>
> Luca
>
> [1] https://quarkus.io/
> [2] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
> [3] https://github.com/quarkusio/quarkus-quickstarts/tree/master/camel-java
> [4]
> https://github.com/lburgazzoli/apache-camel-k-runtime/tree/quarkus-runtime
> [5] https://bit.ly/2HvOrh0
> [6] https://bit.ly/2WDtCbW
> [7]
> https://www.linkedin.com/feed/update/urn:li:activity:6521869236153970688/
>
> ---
> Luca Burgazzoli

Re: [VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Andrea Cosentino]

+1 (binding).

Tested on camel-cassandra.

Il giorno mar 4 giu 2019 alle ore 12:14 Alex Dettinger <
aldettin...@gmail.com> ha scritto:

> +1 (binding)
>
> Many thanks Gregor,
> Alex
>
> On Tue, Jun 4, 2019 at 11:51 AM Nicola Ferraro 
> wrote:
>
> > +1 (binding)
> >
> > Nicola
> >
> > On Tue, Jun 4, 2019 at 11:46 AM Luca Burgazzoli 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > ---
> > > Luca Burgazzoli
> > >
> > >
> > > On Tue, Jun 4, 2019 at 11:40 AM Claus Ibsen 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Tested with CiA2 source code.
> > > >
> > > > On Tue, Jun 4, 2019 at 8:59 AM Gregor Zurowski <
> > gre...@list.zurowski.org
> > > >
> > > > wrote:
> > > > >
> > > > > Hi Everyone:
> > > > >
> > > > > This is the second vote to release Apache Camel 3.0.0-M3, the third
> > > > > milestone towards a new 3.0.0 major release with currently 653
> > > > > improvements and fixes. The first vote was cancelled due to issues
> > > > > found while testing the first release candidate. The necessary
> fixes
> > > > > [1,2] were applied and this new release candidate was created.
> > > > >
> > > > > Release notes:
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
> > > > >
> > > > > Staging repository:
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1139/
> > > > >
> > > > > Tarballs:
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/
> > > > >
> > > > > Tag:
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M3
> > > > >
> > > > > Please test this release candidate and cast your vote.
> > > > > [ ] +1 Release the binary as Apache Camel 3.0.0-M3
> > > > > [ ] -1 Veto the release (provide specific comments)
> > > > >
> > > > > The vote is open for at least 72 hours.
> > > > >
> > > > > Thanks,
> > > > > Gregor
> > > > >
> > > > > [1] Fixed OSGi type converter not loading the core fallback
> > > > > converters:
> > > >
> > >
> >
> https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
> > > > > [2] Fix HealthCheckRegistry and HealthCheckService setters:
> > > > >
> > > >
> > >
> >
> https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e
> > > >
> > > >
> > > >
> > > > --
> > > > Claus Ibsen
> > > > -
> > > > http://davsclaus.com @davsclaus
> > > > Camel in Action 2: https://www.manning.com/ibsen2
> > > >
> > >
> >
>

Re: [VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Alex Dettinger]

+1 (binding)

Many thanks Gregor,
Alex

On Tue, Jun 4, 2019 at 11:51 AM Nicola Ferraro  wrote:

> +1 (binding)
>
> Nicola
>
> On Tue, Jun 4, 2019 at 11:46 AM Luca Burgazzoli 
> wrote:
>
> > +1 (binding)
> >
> > ---
> > Luca Burgazzoli
> >
> >
> > On Tue, Jun 4, 2019 at 11:40 AM Claus Ibsen 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Tested with CiA2 source code.
> > >
> > > On Tue, Jun 4, 2019 at 8:59 AM Gregor Zurowski <
> gre...@list.zurowski.org
> > >
> > > wrote:
> > > >
> > > > Hi Everyone:
> > > >
> > > > This is the second vote to release Apache Camel 3.0.0-M3, the third
> > > > milestone towards a new 3.0.0 major release with currently 653
> > > > improvements and fixes. The first vote was cancelled due to issues
> > > > found while testing the first release candidate. The necessary fixes
> > > > [1,2] were applied and this new release candidate was created.
> > > >
> > > > Release notes:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
> > > >
> > > > Staging repository:
> > > >
> > https://repository.apache.org/content/repositories/orgapachecamel-1139/
> > > >
> > > > Tarballs:
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/
> > > >
> > > > Tag:
> > >
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M3
> > > >
> > > > Please test this release candidate and cast your vote.
> > > > [ ] +1 Release the binary as Apache Camel 3.0.0-M3
> > > > [ ] -1 Veto the release (provide specific comments)
> > > >
> > > > The vote is open for at least 72 hours.
> > > >
> > > > Thanks,
> > > > Gregor
> > > >
> > > > [1] Fixed OSGi type converter not loading the core fallback
> > > > converters:
> > >
> >
> https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
> > > > [2] Fix HealthCheckRegistry and HealthCheckService setters:
> > > >
> > >
> >
> https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e
> > >
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
> >
>

Re: [VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Nicola Ferraro]

+1 (binding)

Nicola

On Tue, Jun 4, 2019 at 11:46 AM Luca Burgazzoli 
wrote:

> +1 (binding)
>
> ---
> Luca Burgazzoli
>
>
> On Tue, Jun 4, 2019 at 11:40 AM Claus Ibsen  wrote:
>
> > +1 (binding)
> >
> > Tested with CiA2 source code.
> >
> > On Tue, Jun 4, 2019 at 8:59 AM Gregor Zurowski  >
> > wrote:
> > >
> > > Hi Everyone:
> > >
> > > This is the second vote to release Apache Camel 3.0.0-M3, the third
> > > milestone towards a new 3.0.0 major release with currently 653
> > > improvements and fixes. The first vote was cancelled due to issues
> > > found while testing the first release candidate. The necessary fixes
> > > [1,2] were applied and this new release candidate was created.
> > >
> > > Release notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachecamel-1139/
> > >
> > > Tarballs:
> >
> https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/
> > >
> > > Tag:
> >
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M3
> > >
> > > Please test this release candidate and cast your vote.
> > > [ ] +1 Release the binary as Apache Camel 3.0.0-M3
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > The vote is open for at least 72 hours.
> > >
> > > Thanks,
> > > Gregor
> > >
> > > [1] Fixed OSGi type converter not loading the core fallback
> > > converters:
> >
> https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
> > > [2] Fix HealthCheckRegistry and HealthCheckService setters:
> > >
> >
> https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e
> >
> >
> >
> > --
> > Claus Ibsen
> > -
> > http://davsclaus.com @davsclaus
> > Camel in Action 2: https://www.manning.com/ibsen2
> >
>

Re: [VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Luca Burgazzoli]

+1 (binding)

---
Luca Burgazzoli


On Tue, Jun 4, 2019 at 11:40 AM Claus Ibsen  wrote:

> +1 (binding)
>
> Tested with CiA2 source code.
>
> On Tue, Jun 4, 2019 at 8:59 AM Gregor Zurowski 
> wrote:
> >
> > Hi Everyone:
> >
> > This is the second vote to release Apache Camel 3.0.0-M3, the third
> > milestone towards a new 3.0.0 major release with currently 653
> > improvements and fixes. The first vote was cancelled due to issues
> > found while testing the first release candidate. The necessary fixes
> > [1,2] were applied and this new release candidate was created.
> >
> > Release notes:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachecamel-1139/
> >
> > Tarballs:
> https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/
> >
> > Tag:
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M3
> >
> > Please test this release candidate and cast your vote.
> > [ ] +1 Release the binary as Apache Camel 3.0.0-M3
> > [ ] -1 Veto the release (provide specific comments)
> >
> > The vote is open for at least 72 hours.
> >
> > Thanks,
> > Gregor
> >
> > [1] Fixed OSGi type converter not loading the core fallback
> > converters:
> https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
> > [2] Fix HealthCheckRegistry and HealthCheckService setters:
> >
> https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Quarkus

[Luca Burgazzoli]

Hi,

In the past months some folks at Red Hat have been working on the
integration between Apache Camel and Quarkus. For those not familiar
with the topic, Quarkus is a new Apache 2 licensed Cloud Native Java
framework tailored for GraalVM and HotSpot that bring fast startup
and low memory footprint to Java based application by leverage clever
build time optimizations and AOT compilation through Substrate VM [1].

The result of the experimentation is available in the Quarkus
repository [2][3] and I’m also working on an experimental branch
on Camel K [4] to bring Quarkus on the K side based on my latest
blog “Adventures in GraalVM: polyglot Camel (k) native routes
with Quarkus”  [5]

I do believe that both communities can benefit from a collaboration:

Apache Camel can benefit from Quarkus to become
a) Even more suitable for microservices
b) Suitable for serverless workloads as Quarkus among others enables
   built-time warmup of the Camel Context, and elimination of dead-code
   (code that was only used during warmup) which is a key enabler for
   very fast start-up and low memory footprint Apache Camel can be on
   the innovative forefront with a cloud native Java stack for running
   modern serverless workloads on Kubernetes/Knative with Camel K and
   Camel Quarkus

So I’m proposing to officially support Quarkus in Apache Camel’s main
repository (or a dedicated one if it suits better) by creating a new
platform along with those we support as today (Spring Boot, Karaf).

Quarkus’ people is keen to donate the code related to Apache Camel
hosted in theirs repository to the Apache Software foundation.

There has been some other users in the community whom have tried
Quarkus and Camel together and written blogs [6] about their experience,
and Claus also posted a quick gif animation of native compiled Camel
with Quarkus starting up in 7 milliseconds and taking up only 15mb
of memory [7].

Thoughts ?

Luca

[1] https://quarkus.io/
[2] https://github.com/quarkusio/quarkus/tree/master/extensions/camel
[3] https://github.com/quarkusio/quarkus-quickstarts/tree/master/camel-java
[4]
https://github.com/lburgazzoli/apache-camel-k-runtime/tree/quarkus-runtime
[5] https://bit.ly/2HvOrh0
[6] https://bit.ly/2WDtCbW
[7]
https://www.linkedin.com/feed/update/urn:li:activity:6521869236153970688/

---
Luca Burgazzoli

Re: [VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Claus Ibsen]

+1 (binding)

Tested with CiA2 source code.

On Tue, Jun 4, 2019 at 8:59 AM Gregor Zurowski  wrote:
>
> Hi Everyone:
>
> This is the second vote to release Apache Camel 3.0.0-M3, the third
> milestone towards a new 3.0.0 major release with currently 653
> improvements and fixes. The first vote was cancelled due to issues
> found while testing the first release candidate. The necessary fixes
> [1,2] were applied and this new release candidate was created.
>
> Release notes: 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12315691=12311211
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecamel-1139/
>
> Tarballs: 
> https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/
>
> Tag: 
> https://gitbox.apache.org/repos/asf?p=camel.git;a=tag;h=refs/tags/camel-3.0.0-M3
>
> Please test this release candidate and cast your vote.
> [ ] +1 Release the binary as Apache Camel 3.0.0-M3
> [ ] -1 Veto the release (provide specific comments)
>
> The vote is open for at least 72 hours.
>
> Thanks,
> Gregor
>
> [1] Fixed OSGi type converter not loading the core fallback
> converters: 
> https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
> [2] Fix HealthCheckRegistry and HealthCheckService setters:
> https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e



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

[GitHub] [camel-k-runtime] lburgazzoli opened a new pull request #74: camel-2.x: remove camel 3 bits

[GitBox]

lburgazzoli opened a new pull request #74: camel-2.x: remove camel 3 bits
URL: https://github.com/apache/camel-k-runtime/pull/74
 
 
   Remove camel 3 bits from branch camel-2.x


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti merged pull request #719: Don't automatically install contexts upon platform installation

[GitBox]

astefanutti merged pull request #719: Don't automatically install contexts upon 
platform installation
URL: https://github.com/apache/camel-k/pull/719
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti closed issue #716: Don't automatically install contexts upon platform installation

[GitBox]

astefanutti closed issue #716: Don't automatically install contexts upon 
platform installation
URL: https://github.com/apache/camel-k/issues/716
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #720: Allow to provide custom settings.xml

[GitBox]

lburgazzoli commented on a change in pull request #720:  Allow to provide 
custom settings.xml
URL: https://github.com/apache/camel-k/pull/720#discussion_r290172078
 
 

 ##
 File path: pkg/cmd/install.go
 ##
 @@ -302,6 +356,11 @@ func (o *installCmdOptions) validate(_ *cobra.Command, _ 
[]string) error {
err := errorIfContextIsNotAvailable(schema, context, 
len(o.contexts))
result = multierr.Append(result, err)
}
+
+   if len(o.mavenRpositories) > 0 && o.mavenSettings != "" {
+   result = fmt.Errorf("incompatible options combinations: you 
canno set both mavenRpository and mavenSettings")
 
 Review comment:
   :(


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] lburgazzoli commented on a change in pull request #720: Allow to provide custom settings.xml

[GitBox]

lburgazzoli commented on a change in pull request #720:  Allow to provide 
custom settings.xml
URL: https://github.com/apache/camel-k/pull/720#discussion_r290172033
 
 

 ##
 File path: pkg/cmd/install.go
 ##
 @@ -88,23 +97,23 @@ func newCmdInstall(rootCmdOptions *RootCmdOptions) 
*cobra.Command {
 
 type installCmdOptions struct {
*RootCmdOptions
-   wait bool
-   clusterSetupOnly bool
-   skipClusterSetup bool
-   exampleSetup bool
-   snapshotRepositories bool
-   outputFormat string
-   camelVersion string
-   runtimeVersion   string
-   baseImagestring
-   operatorImagestring
-   localRepository  string
-   buildStrategystring
-   buildTimeout string
-   repositories []string
-   properties   []string
-   contexts []string
-   registry v1alpha1.IntegrationPlatformRegistrySpec
+   wait bool
+   clusterSetupOnly bool
+   skipClusterSetup bool
+   exampleSetup bool
+   outputFormat string
+   camelVersion string
+   runtimeVersion   string
+   baseImagestring
+   operatorImagestring
+   localRepository  string
+   buildStrategystring
+   buildTimeout string
+   mavenRpositories []string
 
 Review comment:
   :(


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti merged pull request #721: chore(build): remove test artifacts

[GitBox]

astefanutti merged pull request #721: chore(build): remove test artifacts
URL: https://github.com/apache/camel-k/pull/721
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti commented on a change in pull request #720: Allow to provide custom settings.xml

[GitBox]

astefanutti commented on a change in pull request #720:  Allow to provide 
custom settings.xml
URL: https://github.com/apache/camel-k/pull/720#discussion_r290171509
 
 

 ##
 File path: pkg/cmd/install.go
 ##
 @@ -210,6 +200,68 @@ func (o *installCmdOptions) install(_ *cobra.Command, _ 
[]string) error {
platform.Spec.Build.Timeout.Duration = d
}
 
+   if len(o.repositories) > 0 {
+   o.mavenSettings = 
fmt.Sprintf("configmap:%s-maven-settings/settings.xml", platform.Name)
+
+   settings := maven.NewSettings()
 
 Review comment:
   Right, it's still need a merge strategy, which can be addressed later.


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti commented on a change in pull request #720: Allow to provide custom settings.xml

[GitBox]

astefanutti commented on a change in pull request #720:  Allow to provide 
custom settings.xml
URL: https://github.com/apache/camel-k/pull/720#discussion_r290170747
 
 

 ##
 File path: pkg/cmd/install.go
 ##
 @@ -302,6 +356,11 @@ func (o *installCmdOptions) validate(_ *cobra.Command, _ 
[]string) error {
err := errorIfContextIsNotAvailable(schema, context, 
len(o.contexts))
result = multierr.Append(result, err)
}
+
+   if len(o.mavenRpositories) > 0 && o.mavenSettings != "" {
+   result = fmt.Errorf("incompatible options combinations: you 
canno set both mavenRpository and mavenSettings")
 
 Review comment:
   `canno` -> `cannot`, `mavenRpository` -> `mavenRepository`


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] [camel-k] astefanutti commented on a change in pull request #720: Allow to provide custom settings.xml

[GitBox]

astefanutti commented on a change in pull request #720:  Allow to provide 
custom settings.xml
URL: https://github.com/apache/camel-k/pull/720#discussion_r290170396
 
 

 ##
 File path: pkg/cmd/install.go
 ##
 @@ -88,23 +97,23 @@ func newCmdInstall(rootCmdOptions *RootCmdOptions) 
*cobra.Command {
 
 type installCmdOptions struct {
*RootCmdOptions
-   wait bool
-   clusterSetupOnly bool
-   skipClusterSetup bool
-   exampleSetup bool
-   snapshotRepositories bool
-   outputFormat string
-   camelVersion string
-   runtimeVersion   string
-   baseImagestring
-   operatorImagestring
-   localRepository  string
-   buildStrategystring
-   buildTimeout string
-   repositories []string
-   properties   []string
-   contexts []string
-   registry v1alpha1.IntegrationPlatformRegistrySpec
+   wait bool
+   clusterSetupOnly bool
+   skipClusterSetup bool
+   exampleSetup bool
+   outputFormat string
+   camelVersion string
+   runtimeVersion   string
+   baseImagestring
+   operatorImagestring
+   localRepository  string
+   buildStrategystring
+   buildTimeout string
+   mavenRpositories []string
 
 Review comment:
   `mavenRpositories` -> `mavenRepositories`


This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[VOTE] Release Apache Camel 3.0.0-M3 (Milestone 3) (Attempt #2)

[Gregor Zurowski]

Hi Everyone:

This is the second vote to release Apache Camel 3.0.0-M3, the third
milestone towards a new 3.0.0 major release with currently 653
improvements and fixes. The first vote was cancelled due to issues
found while testing the first release candidate. The necessary fixes
[1,2] were applied and this new release candidate was created.

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

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

Tarballs: 
https://repository.apache.org/content/repositories/orgapachecamel-1139/org/apache/camel/apache-camel/3.0.0-M3/

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

Please test this release candidate and cast your vote.
[ ] +1 Release the binary as Apache Camel 3.0.0-M3
[ ] -1 Veto the release (provide specific comments)

The vote is open for at least 72 hours.

Thanks,
Gregor

[1] Fixed OSGi type converter not loading the core fallback
converters: 
https://github.com/apache/camel/commit/369c382ea2dfab3384478c2f12953e6ca6a16776
[2] Fix HealthCheckRegistry and HealthCheckService setters:
https://github.com/apache/camel/commit/d87f5d55d8bf738bc6a62455542456ecf78e1b9e