Camel.trunk.notest - Build # 2891 - Still Failing
The Apache Jenkins build system has built Camel.trunk.notest (build #2891) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/2891/ to view the results.
Camel.2.17.x.notest - Build # 131 - Failure
The Apache Jenkins build system has built Camel.2.17.x.notest (build #131) Status: Failure Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/131/ to view the results.
Re: New Apache Camel Logo
+1 --- Luca Burgazzoli On Thu, Sep 29, 2016 at 4:50 PM, Andrea Cosentino wrote: > Absolutely +1. > > We need a new logo! > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > On Thursday, September 29, 2016 4:47 PM, Claus Ibsen > wrote: > Hi > > The old Apache Camel logo is a bit out dated, and we have in the past > talked about a new logo. > > Then Jakub Korab posed this tweet > https://twitter.com/jakekorab/status/780333769358184449 > > Seems like there is a design team that did a great logo for bash. > > So maybe we can ask if they would consider try to do an Apache Camel logo. > > Of course anyone else is welcome to attempt to do a better logo. > > It would be good if the logo can be in vector and bitmap. > So with vector we can do a SVG and for bitmap we can have a PNG / JPEG etc. > Also maybe for vector we can try to do a little .ico file for web browser. > > > Any comments or thoughts? > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.18 Release
And obviously, thanks Gregor! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:59 PM, Andrea Cosentino wrote: And obviously, thanks Gregor! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:59 PM, Andrea Cosentino wrote: I'll try to align everything during tomorrow. So I guess It will be ok. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:57 PM, Gregor Zurowski wrote: Hi Claus, I will be able to create a release candidate for 2.18 this weekend, so we could start the vote around Sunday/Monday. Does that work for everyone? Thanks, Gregor On Thu, Sep 29, 2016 at 3:17 PM, Claus Ibsen wrote: > Hi Gregor > > When Andreas have updated the SMX bundles tomorrow, then we should be > ready to start cutting a RC. > > I wonder when you have time in your calendar to cut a release? > > > > On Wed, Sep 28, 2016 at 9:18 AM, Andrea Cosentino > wrote: >> Hello Claus, >> >> We are on vote now. Hopefully we should be able to have the bundles on >> Friday. >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix Committer >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> On Wednesday, September 28, 2016 9:17 AM, Claus Ibsen >> wrote: >> Hi Andrea >> >> How is it going with the SMX bundle release? >> >> >> >> On Fri, Sep 23, 2016 at 4:43 PM, Andrea Cosentino >> wrote: >>> During the weekend JB will cut release for SMX bundles. >>> >>> So we should be able to align karaf features and be ready to release by the >>> middle of the next week. >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:36 AM, Andrea Cosentino >>> wrote: >>> I physically removed the folders of the starters and I pulled master >>> aligning to the codebase. >>> >>> This way it should work fine. >>> >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:26 AM, Nicola Ferraro >>> wrote: >>> That Happened also to Andrea yesterday. The cause should be the blacklist, >>> that is hardcoded in the camel-package maven plugin, so you have to rebuild >>> the plugin first. >>> The plugin does not delete the starters, it is just able to create them. >>> They have been deleted from the repo, but probably some git clients leave >>> the empty folders, so I pushed right now some changes to improve the >>> detection of all required starters. >>> >>> But once they are created by chance, you have to delete them manually. >>> Deleting them and doing a full rebuild should solve the problem, because >>> the plugin is at the top of the reactor list. Just a full rebuild after the >>> update should be sufficient for the others (I hope). >>> >>> I just did a check with latest code from Apache master. >>> >>> >>> On Thu, Sep 22, 2016 at 8:35 AM, Claus Ibsen wrote: >>> Hi Nicola When I build the latest code then some -starter modules are generated for modules that ought to be blacklisted components-starter/camel-ejb-starter/ components-starter/camel-ibatis-starter/ components-starter/camel-jclouds-starter/ components-starter/camel-quartz-starter/ On Fri, Sep 16, 2016 at 11:01 AM, Nicola Ferraro wrote: > Hi Claus, I started working on that this morning. > I think I'll provide the new BOM and related updates early next week. > > > > > > On Fri, Sep 16, 2016 at 9:38 AM, Claus Ibsen wrote: > >> Hi Nicola >> >> How does your calendar look like? I wonder if you have time to work >> more on this Camel and Spring Boot stuff? >> >> I am afraid this one is the major task we have left before we can get >> started on the Camel 2.18 release and IMHO first class Spring Boot >> support is a major win/goal for Camel. >> >> So the work is very important, and its been awesome what you have >> done. Really love that we have integration tests, and also separated >> the auto stuff code from the existing components so there is cle
Re: Getting ready for Apache Camel 2.18 Release
I'll try to align everything during tomorrow. So I guess It will be ok. -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:57 PM, Gregor Zurowski wrote: Hi Claus, I will be able to create a release candidate for 2.18 this weekend, so we could start the vote around Sunday/Monday. Does that work for everyone? Thanks, Gregor On Thu, Sep 29, 2016 at 3:17 PM, Claus Ibsen wrote: > Hi Gregor > > When Andreas have updated the SMX bundles tomorrow, then we should be > ready to start cutting a RC. > > I wonder when you have time in your calendar to cut a release? > > > > On Wed, Sep 28, 2016 at 9:18 AM, Andrea Cosentino > wrote: >> Hello Claus, >> >> We are on vote now. Hopefully we should be able to have the bundles on >> Friday. >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix Committer >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> On Wednesday, September 28, 2016 9:17 AM, Claus Ibsen >> wrote: >> Hi Andrea >> >> How is it going with the SMX bundle release? >> >> >> >> On Fri, Sep 23, 2016 at 4:43 PM, Andrea Cosentino >> wrote: >>> During the weekend JB will cut release for SMX bundles. >>> >>> So we should be able to align karaf features and be ready to release by the >>> middle of the next week. >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:36 AM, Andrea Cosentino >>> wrote: >>> I physically removed the folders of the starters and I pulled master >>> aligning to the codebase. >>> >>> This way it should work fine. >>> >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:26 AM, Nicola Ferraro >>> wrote: >>> That Happened also to Andrea yesterday. The cause should be the blacklist, >>> that is hardcoded in the camel-package maven plugin, so you have to rebuild >>> the plugin first. >>> The plugin does not delete the starters, it is just able to create them. >>> They have been deleted from the repo, but probably some git clients leave >>> the empty folders, so I pushed right now some changes to improve the >>> detection of all required starters. >>> >>> But once they are created by chance, you have to delete them manually. >>> Deleting them and doing a full rebuild should solve the problem, because >>> the plugin is at the top of the reactor list. Just a full rebuild after the >>> update should be sufficient for the others (I hope). >>> >>> I just did a check with latest code from Apache master. >>> >>> >>> On Thu, Sep 22, 2016 at 8:35 AM, Claus Ibsen wrote: >>> Hi Nicola When I build the latest code then some -starter modules are generated for modules that ought to be blacklisted components-starter/camel-ejb-starter/ components-starter/camel-ibatis-starter/ components-starter/camel-jclouds-starter/ components-starter/camel-quartz-starter/ On Fri, Sep 16, 2016 at 11:01 AM, Nicola Ferraro wrote: > Hi Claus, I started working on that this morning. > I think I'll provide the new BOM and related updates early next week. > > > > > > On Fri, Sep 16, 2016 at 9:38 AM, Claus Ibsen wrote: > >> Hi Nicola >> >> How does your calendar look like? I wonder if you have time to work >> more on this Camel and Spring Boot stuff? >> >> I am afraid this one is the major task we have left before we can get >> started on the Camel 2.18 release and IMHO first class Spring Boot >> support is a major win/goal for Camel. >> >> So the work is very important, and its been awesome what you have >> done. Really love that we have integration tests, and also separated >> the auto stuff code from the existing components so there is clean >> separation. >> >> >> >> >> On Wed, Sep 14, 2016 at 3:32 PM, Nicola Ferraro >> wrote: >> > Well, it was one of the drawbacks of the approach. Forcing users to >> include >> > *only* the camel BOM allows us to completely control the dependencies, >> but >> > it's probably a too strict requirement for users. >> > >> > We can also provide a option 1+2: i.e. a auto-generated Camel BOM without >> > any conflict with the spring-boot one (conflicts verified by eg. a maven >> > plugin). >
Re: New Apache Camel Logo
Absolutely +1. We need a new logo! -- Andrea Cosentino -- Apache Camel PMC Member Apache Karaf Committer Apache Servicemix Committer Email: ancosen1...@yahoo.com Twitter: @oscerd2 Github: oscerd On Thursday, September 29, 2016 4:47 PM, Claus Ibsen wrote: Hi The old Apache Camel logo is a bit out dated, and we have in the past talked about a new logo. Then Jakub Korab posed this tweet https://twitter.com/jakekorab/status/780333769358184449 Seems like there is a design team that did a great logo for bash. So maybe we can ask if they would consider try to do an Apache Camel logo. Of course anyone else is welcome to attempt to do a better logo. It would be good if the logo can be in vector and bitmap. So with vector we can do a SVG and for bitmap we can have a PNG / JPEG etc. Also maybe for vector we can try to do a little .ico file for web browser. Any comments or thoughts? -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.18 Release
Hi Claus, I will be able to create a release candidate for 2.18 this weekend, so we could start the vote around Sunday/Monday. Does that work for everyone? Thanks, Gregor On Thu, Sep 29, 2016 at 3:17 PM, Claus Ibsen wrote: > Hi Gregor > > When Andreas have updated the SMX bundles tomorrow, then we should be > ready to start cutting a RC. > > I wonder when you have time in your calendar to cut a release? > > > > On Wed, Sep 28, 2016 at 9:18 AM, Andrea Cosentino > wrote: >> Hello Claus, >> >> We are on vote now. Hopefully we should be able to have the bundles on >> Friday. >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix Committer >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> On Wednesday, September 28, 2016 9:17 AM, Claus Ibsen >> wrote: >> Hi Andrea >> >> How is it going with the SMX bundle release? >> >> >> >> On Fri, Sep 23, 2016 at 4:43 PM, Andrea Cosentino >> wrote: >>> During the weekend JB will cut release for SMX bundles. >>> >>> So we should be able to align karaf features and be ready to release by the >>> middle of the next week. >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:36 AM, Andrea Cosentino >>> wrote: >>> I physically removed the folders of the starters and I pulled master >>> aligning to the codebase. >>> >>> This way it should work fine. >>> >>> -- >>> Andrea Cosentino >>> -- >>> Apache Camel PMC Member >>> Apache Karaf Committer >>> Apache Servicemix Committer >>> Email: ancosen1...@yahoo.com >>> Twitter: @oscerd2 >>> Github: oscerd >>> >>> >>> >>> On Thursday, September 22, 2016 9:26 AM, Nicola Ferraro >>> wrote: >>> That Happened also to Andrea yesterday. The cause should be the blacklist, >>> that is hardcoded in the camel-package maven plugin, so you have to rebuild >>> the plugin first. >>> The plugin does not delete the starters, it is just able to create them. >>> They have been deleted from the repo, but probably some git clients leave >>> the empty folders, so I pushed right now some changes to improve the >>> detection of all required starters. >>> >>> But once they are created by chance, you have to delete them manually. >>> Deleting them and doing a full rebuild should solve the problem, because >>> the plugin is at the top of the reactor list. Just a full rebuild after the >>> update should be sufficient for the others (I hope). >>> >>> I just did a check with latest code from Apache master. >>> >>> >>> On Thu, Sep 22, 2016 at 8:35 AM, Claus Ibsen wrote: >>> Hi Nicola When I build the latest code then some -starter modules are generated for modules that ought to be blacklisted components-starter/camel-ejb-starter/ components-starter/camel-ibatis-starter/ components-starter/camel-jclouds-starter/ components-starter/camel-quartz-starter/ On Fri, Sep 16, 2016 at 11:01 AM, Nicola Ferraro wrote: > Hi Claus, I started working on that this morning. > I think I'll provide the new BOM and related updates early next week. > > > > > > On Fri, Sep 16, 2016 at 9:38 AM, Claus Ibsen wrote: > >> Hi Nicola >> >> How does your calendar look like? I wonder if you have time to work >> more on this Camel and Spring Boot stuff? >> >> I am afraid this one is the major task we have left before we can get >> started on the Camel 2.18 release and IMHO first class Spring Boot >> support is a major win/goal for Camel. >> >> So the work is very important, and its been awesome what you have >> done. Really love that we have integration tests, and also separated >> the auto stuff code from the existing components so there is clean >> separation. >> >> >> >> >> On Wed, Sep 14, 2016 at 3:32 PM, Nicola Ferraro >> wrote: >> > Well, it was one of the drawbacks of the approach. Forcing users to >> include >> > *only* the camel BOM allows us to completely control the dependencies, >> but >> > it's probably a too strict requirement for users. >> > >> > We can also provide a option 1+2: i.e. a auto-generated Camel BOM without >> > any conflict with the spring-boot one (conflicts verified by eg. a maven >> > plugin). >> > Users will be able to import it in any order but, of course, some >> > components will not work because we cannot override what's in the >> > spring-boot BOM (unless the users force a different version in their pom, >> > but it's up to them). >> > >> > It makes more sense.. >> > What do you think
New Apache Camel Logo
Hi The old Apache Camel logo is a bit out dated, and we have in the past talked about a new logo. Then Jakub Korab posed this tweet https://twitter.com/jakekorab/status/780333769358184449 Seems like there is a design team that did a great logo for bash. So maybe we can ask if they would consider try to do an Apache Camel logo. Of course anyone else is welcome to attempt to do a better logo. It would be good if the logo can be in vector and bitmap. So with vector we can do a SVG and for bitmap we can have a PNG / JPEG etc. Also maybe for vector we can try to do a little .ico file for web browser. Any comments or thoughts? -- Claus Ibsen - http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
Re: Getting ready for Apache Camel 2.18 Release
Hi Gregor When Andreas have updated the SMX bundles tomorrow, then we should be ready to start cutting a RC. I wonder when you have time in your calendar to cut a release? On Wed, Sep 28, 2016 at 9:18 AM, Andrea Cosentino wrote: > Hello Claus, > > We are on vote now. Hopefully we should be able to have the bundles on Friday. > -- > Andrea Cosentino > -- > Apache Camel PMC Member > Apache Karaf Committer > Apache Servicemix Committer > Email: ancosen1...@yahoo.com > Twitter: @oscerd2 > Github: oscerd > > > > On Wednesday, September 28, 2016 9:17 AM, Claus Ibsen > wrote: > Hi Andrea > > How is it going with the SMX bundle release? > > > > On Fri, Sep 23, 2016 at 4:43 PM, Andrea Cosentino > wrote: >> During the weekend JB will cut release for SMX bundles. >> >> So we should be able to align karaf features and be ready to release by the >> middle of the next week. >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix Committer >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> On Thursday, September 22, 2016 9:36 AM, Andrea Cosentino >> wrote: >> I physically removed the folders of the starters and I pulled master >> aligning to the codebase. >> >> This way it should work fine. >> >> -- >> Andrea Cosentino >> -- >> Apache Camel PMC Member >> Apache Karaf Committer >> Apache Servicemix Committer >> Email: ancosen1...@yahoo.com >> Twitter: @oscerd2 >> Github: oscerd >> >> >> >> On Thursday, September 22, 2016 9:26 AM, Nicola Ferraro >> wrote: >> That Happened also to Andrea yesterday. The cause should be the blacklist, >> that is hardcoded in the camel-package maven plugin, so you have to rebuild >> the plugin first. >> The plugin does not delete the starters, it is just able to create them. >> They have been deleted from the repo, but probably some git clients leave >> the empty folders, so I pushed right now some changes to improve the >> detection of all required starters. >> >> But once they are created by chance, you have to delete them manually. >> Deleting them and doing a full rebuild should solve the problem, because >> the plugin is at the top of the reactor list. Just a full rebuild after the >> update should be sufficient for the others (I hope). >> >> I just did a check with latest code from Apache master. >> >> >> On Thu, Sep 22, 2016 at 8:35 AM, Claus Ibsen wrote: >> >>> Hi Nicola >>> >>> When I build the latest code then some -starter modules are generated >>> for modules that ought to be blacklisted >>> >>> components-starter/camel-ejb-starter/ >>> components-starter/camel-ibatis-starter/ >>> components-starter/camel-jclouds-starter/ >>> components-starter/camel-quartz-starter/ >>> >>> On Fri, Sep 16, 2016 at 11:01 AM, Nicola Ferraro >>> wrote: >>> > Hi Claus, I started working on that this morning. >>> > I think I'll provide the new BOM and related updates early next week. >>> > >>> > >>> > >>> > >>> > >>> > On Fri, Sep 16, 2016 at 9:38 AM, Claus Ibsen >>> wrote: >>> > >>> >> Hi Nicola >>> >> >>> >> How does your calendar look like? I wonder if you have time to work >>> >> more on this Camel and Spring Boot stuff? >>> >> >>> >> I am afraid this one is the major task we have left before we can get >>> >> started on the Camel 2.18 release and IMHO first class Spring Boot >>> >> support is a major win/goal for Camel. >>> >> >>> >> So the work is very important, and its been awesome what you have >>> >> done. Really love that we have integration tests, and also separated >>> >> the auto stuff code from the existing components so there is clean >>> >> separation. >>> >> >>> >> >>> >> >>> >> >>> >> On Wed, Sep 14, 2016 at 3:32 PM, Nicola Ferraro >>> >> wrote: >>> >> > Well, it was one of the drawbacks of the approach. Forcing users to >>> >> include >>> >> > *only* the camel BOM allows us to completely control the dependencies, >>> >> but >>> >> > it's probably a too strict requirement for users. >>> >> > >>> >> > We can also provide a option 1+2: i.e. a auto-generated Camel BOM >>> without >>> >> > any conflict with the spring-boot one (conflicts verified by eg. a >>> maven >>> >> > plugin). >>> >> > Users will be able to import it in any order but, of course, some >>> >> > components will not work because we cannot override what's in the >>> >> > spring-boot BOM (unless the users force a different version in their >>> pom, >>> >> > but it's up to them). >>> >> > >>> >> > It makes more sense.. >>> >> > What do you think about it? >>> >> > >>> >> > >>> >> > >>> >> > On Wed, Sep 14, 2016 at 9:46 AM, Claus Ibsen >>> >> wrote: >>> >> > >>> >> >> Hi Nicola >>> >> >> >>> >> >> Great work on all this Spring Boot starter stuff. >>> >> >> >>> >> >> I would like to discuss/hear more about the #1 option you listed on >>> >> >> https://github.com/apache/camel/pull/1164 >>> >> >> >>> >> >> I think that end users w
[GitHub] camel pull request #1188: CAMEL-10347: camel-scr todos and polish
Github user yuruki closed the pull request at: https://github.com/apache/camel/pull/1188 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
