Re: [VOTE] Release Apache Camel 2.13.2/2.12.4

+1 for both Willem Jiang 2 July 2014 03:18 Hi This is a vote to release Apache Camel 2.13.2 and 2.12.4. Release notes: 2.13.2 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326817&styleName=Html&projectId=12311211 2.12.4 https://issues.apac

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

On 1 Dec 2013, at 13:25, dk...@apache.org [via Camel] wrote: > > > > > So any 3rd party tool that aids developers, can't be run as a maven target > > unless its completely branded and controlled by the Camel PMC is the stance > > you are taking. > > If the maven plugin is part of Camel and

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

t; does this integration. So the dependency is simply from hawtio to camel. > >> For the users this does not make a difference in usability but technically > >> it is cleaner. > >> > >> Christian > >> > >> Am 01.12.2013 09:46, schrieb Rob D

Re: git commit: CAMEL-7023: Added hawtio goal to camel maven plugin.

dk...@apache.org wrote > Having no way for this PMC to control the display of the Camel route *IS* > a technical justification. If we as a PMC wanted to remove columns, add > new columns for new features, change the order of stuff, etc…. *WE* have > no way to do so. > > Having no way to cha

Re: [DISCUSS] Message Store

+1 On 25 Oct 2012, at 12:44, Hadrian Zbarcea wrote: > There will be quite a few Camel committers at ACEU. Technical discussions > must be inclusive of the community and take place on this dev@ list though. > > Hadrian > > > On 10/25/2012 03:47 AM, Christian Ohr wrote: >> Let me quickly sum

Re: [camel-extra] Changed groupId and package name of camel-esper-demo

+1 for 2 x e + 1 s On 22 Oct 2012, at 21:05, Henryk Konsek wrote: >> The package name should be >> org.apacheextras (2 'e's, 1 's'). > > Apparently in one of my previous posts I accidentally removed 's' from > the package name. Probably that confused Hadrian. Sorry for that. > > Just to make

Re: [VOTE] Release Apache Camel 2.10.2

+1 On 11 Oct 2012, at 18:43, Hadrian Zbarcea wrote: > A new patch release candidate apache-camel-2.9.4 final is out with > approximately 71 issues resolved so far: improvements and bug fixes [1]. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/orgapach

Re: ASF Board Report - Initial Reminder for Sep 2012

Hi Christian, FuseSource hasn't been acquired by Red Hat yet - the process is continuing. thanks, Rob On 3 Sep 2012, at 22:49, Christian Mueller wrote: > I plan to submit the September 2012 Apache board report until 11th of > September. I already put something together [1]. Feel free to commen

Re: [DISCUSS] - Camel Maven Archetypes - Generating files with ASF license headers

I think this thread is helpful - its from Eclipse - http://www.eclipsezone.com/eclipse/forums/t116081.html On 4 Jul 2012, at 09:19, Christian Schneider wrote: > My current understanding is that you can not assume you are allowed to use > code if it has no license. Is there an exception for gene

Re: [VOTE] Release Apache Camel 2.10.0 (2nd attempt)

+1 On 28 Jun 2012, at 03:39, Hadrian Zbarcea wrote: > A new release candidate apache-camel-2.10.0 final is out with approximately > 483 issues resolved so far: improvements and bug fixes [1]. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/orgapachecam

Re: [DISCUSS] Should camel enforce usage of proper URIs?

This sounds reasonable to me On 21 Jun 2012, at 18:36, Hadrian Zbarcea wrote: > Sounds perfect. That's exactly what I had in mind. You are proposing the > extra setting, which I am perfectly fine with. > > Thanks a bunch, > Hadrian > > On 06/21/2012 01:00 PM, Hiram Chirino wrote: >> How about w

Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints

If you vote had more detail about what you was considering, then artistic feelings wouldn't have come into it :) Why don't you close this vote - and open a new discussion (with more detail?) - so we can try reach a consensus On 21 Jun 2012, at 18:19, Hadrian Zbarcea wrote: > Now finally someth

Re: [VOTE] Camel MUST use valid URIs for identifying and configuring Endpoints

-1 Camel does not need to use valid URIs - I see no real benefit for the user. I'm concerned about any changes that could affect existing users. On 20 Jun 2012, at 01:37, Hadrian Zbarcea wrote: > Using URIs to identify and configure Endpoints is a notable Apache Camel > innovation. This featur

Re: [VOTE] Release Apache Camel 2.8.5

+1 On 23 Apr 2012, at 21:14, Hadrian Zbarcea wrote: > A new patch release candidate apache-camel-2.8.5 is out with approximately 46 > issues resolved: improvements and bug fixes [1]. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/orgapachecamel-085/ >

Re: [VOTE] Add a new mailing list issues@

+1 On 30 Oct 2011, at 19:45, Christian Mueller wrote: > Add a new mailing list iss...@camel.apache.org to which we send all [jira] > messages (which are currently sent to dev@camel.apache.org). > I could imagine we have to much messages in the dev@ mailing list which are > not really interesting f

Re: [DISCUSS] - Trunk as Camel 3.0

Nah - just get on with 3.0. Why would users want to migrate from 2.8.x to 2.9.x instead of waiting for 3.0 ? I don't see the rationale. We've have set the expectation for 3.0 for a while - http://camel.apache.org/camel-30-roadmap.html - there seems no benefit to our end users by dragging our fe

Re: [DISCUSS] - Trunk as Camel 3.0

The reality is that users, want stability and they will be unwilling to move to versions above 2.8.x unless there's a compelling reason to do so. So if they know a 3.0 is in the works, they will wait till that version is GA before considering upgrading. So try to get them to transition easily

Re: [DISCUSS] - Trunk as Camel 3.0

+1 On 23 Sep 2011, at 12:13, Claus Ibsen wrote: > Hi > > I would like to propose that Camel source code currently on trunk is > to be Camel 3.0.0. > And the current code on the 2.8.x branch is to be used for the 2.x > lifetime of Camel. > > The reason for this can be summarized as: > 1) All the

Re: Camel 2.8.2 - Reason for the many backports?

Awesome! - thanks Dan On 21 Sep 2011, at 15:23, Daniel Kulp wrote: > On Wednesday, September 21, 2011 2:53:49 PM Rob Davies wrote: >> For my part it is the principle - at some point this will go wrong - doing >> what Chistian suggested makes a lot of sense. And, users in

Re: Camel 2.8.2 - Reason for the many backports?

sts Dan to do the right thing, but he's > concerned about the precedent he sets for the less talented rest of us who > might go wild and break things. > > Did I get it right? Is there a particular commit that triggered this > question, or is more the principle? > > H

Re: Camel 2.8.2 - Reason for the many backports?

Dan it admirable what you want to do but it would be better to encourage collective best practice - so we do not break backward compatibility on a released branch. That's why discussing adding new features, or changes to dependencies on the DEV list first is a good idea. it will set the pattern

Re: Camel 2.8.2 - Reason for the many backports?

Completely agree - this is accepted practice for software. On 21 Sep 2011, at 02:58, Christian Müller wrote: > +1 for backporting issues which are considered as bug. > +1 for backporting issues which updates a third party library in an bugfix > version. > > All other backports shuld be discussed

Re: [DISCUSS] - API stability in Camel 2.x

Mmm - seems still to be there (on SendDefinition). I'm deriving a class from WireTapDefinition - which can no longer find getUriOrRef() moving from camel 2.7 to 2.8 :) On 8 Sep 2011, at 11:59, Rob Davies wrote: > getUriOrRef() was removed from ProcessDefinition between Camel 2.7 a

Re: [DISCUSS] - API stability in Camel 2.x

getUriOrRef() was removed from ProcessDefinition between Camel 2.7 and Camel 2.8 (not even deprecated) - what's the thinking behind that ? thanks, Rob On 6 Sep 2011, at 12:36, Christian Schneider wrote: > Btw. I just compiled the unchanged camel-extra components against my current > camel t

Re: [DISCUSS] - Dropping Maven 2.x support

Seems a sensible approach On 14 Aug 2011, at 10:35, Claus Ibsen wrote: > Hi > > I wonder if we should consider dropping any official support for Maven > 2.x on the Apache Camel project? > I guess most people is now migrated to Maven 3.0. And the last number > of releases has been done using Maven

Social Event in Washington DC May 23rd.

A few of the FuseSource Apache committers are going to be in the Washington DC area the week of May 23rd for CamelOne. We would like to invite contributors and committers on Apache Camel, ServiceMix, Karaf, ActiveMQ and CXF to a free Community Meet and Greet sponsored by FuseSource on Monday

Re: Editing and removing pages on Apache Camel website without discussing first

I think Books and Getting Started are great too - I would hate to see them deleted On 4 May 2011, at 08:48, Claus Ibsen wrote: > On Wed, May 4, 2011 at 9:21 AM, Rob Davies wrote: >> I've corresponded with Hadrian about this off list. >> >> Whilst I understand

Re: Editing and removing pages on Apache Camel website without discussing first

I've corresponded with Hadrian about this off list. Whilst I understand the sentiment, this policy certainly wasn't clear to me or other PMC members. Whilst there are occasional links to external information, mainly at FuseSource, these are historical and done in the context of providing infor

Re: Editing and removing pages on Apache Camel website without discussing first

thanks Dan - I can remember that conversation on cxf lists - but can't remember seeing anything like that for Camel ? On 3 May 2011, at 18:29, Daniel Kulp wrote: > On Tuesday, May 03, 2011 1:11:12 PM Rob Davies wrote: >> Hi Hadrian, >> >> can you add some more info -

Re: Editing and removing pages on Apache Camel website without discussing first

Hi Hadrian, can you add some more info - I can't find the original thread on this thanks, Rob On 3 May 2011, at 16:52, Hadrian Zbarcea wrote: > No, there are things that are not up to the community to decide. I drew > attention when some changes were made that that was a mistake and my > impr

Re: [VOTE] Release Apache Camel 2.7.1

+1 - thanks for the extra time On 8 Apr 2011, at 22:58, Hadrian Zbarcea wrote: > A patch release apache-camel-2.7.1 is out with approximately 12 issues > resolved: improvements and bug fixes. > > This release targets mostly usability issues related to camel dependencies > (more specifically sl

Re: [VOTE] Release Apache Camel 2.7.1

I would like to extend out the voting time - as this was a raised last thing on Friday - it seems appropriate to extend it out a few days to give folks adequate time to test it thanks, Rob On 8 Apr 2011, at 22:58, Hadrian Zbarcea wrote: > A patch release apache-camel-2.7.1 is out with approxi

Re: [DISCUSS] New Logo

rs, > Hadrian > > > On Mar 29, 2011, at 2:06 AM, Rob Davies wrote: > >> Hadrian - are you wearing your Apache hat when asking that question ? >> >> Yes - these images are variations of the logo for the CamelOne event in May. >> You can compare the logo

Re: [DISCUSS] New Logo

x27;s websites) on your own > website solely as a hyperlink to the specific Apache project website > or to www.apache.org. All other uses of Apache Foo (and similar) > graphic logos must be approved in writing by VP, Apache Brand > Management or a designee. > [...] > > > On

Re: [DISCUSS] New Logo

Hadrian - are you wearing your Apache hat when asking that question ? Yes - these images are variations of the logo for the CamelOne event in May. You can compare the logo here: http://fusesource.com/camelone2011/. they have been done by a professional artist - so why not submit them for consid

Re: [DISCUSS] New Logo

weird - it was a pdf - anybody else not see the attachment (attached) On 28 Mar 2011, at 17:59, Johan Edstrom wrote: > No attachment. > On Mar 28, 2011, at 10:56 AM, Rob Davies wrote: > >> Attached is cartoon camel log with text >> >

Re: [DISCUSS] New Logo

Attached is cartoon camel log with text

Re: [DISCUSS] - Early Camel 2.7 release

+1 On 18 Feb 2011, at 12:19, Claus Ibsen wrote: > Hi > > Now that the major migration efforts for Camel 2.7 is in-house > (JDK1.6,spring3,slf4j, etc.). and the fact that we did this really > fast. > Thanks everyone. > > I would like to propose that we consider doing an earlier release of > Camel

[jira] Resolved: (CAMEL-3672) Make it easier to derive from the Camel model

[ https://issues.apache.org/jira/browse/CAMEL-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved CAMEL-3672. --- Resolution: Fixed Fixed by SVN revision 1071296 > Make it easier to derive from the Camel mo

[jira] Created: (CAMEL-3672) Make it easier to derive from the Camel model

Reporter: Rob Davies Assignee: Rob Davies Fix For: 2.7.0 In order to facilitate the building of derivations of Camel, some methods in builder and model need to use accessors for member variables, and types to allow for sub types -- This message is automatically

Re: [DISCUSS] The future of camel-extra

[2] - best to stay consistent with other apache projects On 5 Feb 2011, at 22:29, Hadrian Zbarcea wrote: > Now that 2.6.0 is out, I planned to give camel-extra a bit more attention. > > There are some changes we need to make to camel-extra and I raised an issue > about it a while ago and added o

[jira] Resolved: (CAMEL-3616) camel-josql doesnot export org.apache.camel.language.sql.*

[ https://issues.apache.org/jira/browse/CAMEL-3616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved CAMEL-3616. --- Resolution: Fixed Fixed by SVN revision 1066494 > camel-josql doesnot exp

[jira] Created: (CAMEL-3616) camel-josql doesnot export org.apache.camel.language.sql.*

Components: camel-sql Affects Versions: 2.6.0, 2.7.0 Reporter: Rob Davies Assignee: Rob Davies Fix For: 2.7.0 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [VOTE] Release Apache Camel 2.5.0

+1 On 25 Oct 2010, at 22:19, Hadrian Zbarcea wrote: > A new release apache-camel-2.5.0 is out with approximately 300 issues > resolved: new features, improvements and bug fixes. > > Please find the staging repo here: > https://repository.apache.org/content/repositories/orgapachecamel-004/ > The

Re: [VOTE] Release Apache Camel 2.0.0

[ ] +1 Release the binary as Apache Camel 2.0-M3 [ ] -1 Veto the release (provide specific comments) Vote is open for 72 hours. The Camel Riders Rob Davies I work here: http://fusesource.com My Blog: http://rajdavies.blogspot.com/ I'm writing this: http://www.manning.com/snyder/

Re: [VOTE] Release Apache Camel 2.0-M3

release (provide specific comments) Vote is open for 72 hours. Here's my +1 Hadrian Rob Davies I work here: http://fusesource.com My Blog: http://rajdavies.blogspot.com/ I'm writing this: http://www.manning.com/snyder/