Re: [DISCUSS] How to improve the documentation of new functionality (for older releases)

I would also try to keep the documentation as simple as possible. Documentation is often maintained by different people than the developers. Currently we have the advantage that people can help with the documentation without being developers. This is an easy way to do first steps in camel. Using

Re: Camel Spring Batch

Hi This sounds great. You are very welcome to look into how to integrate Camel and Spring Batch. On Sun, Feb 5, 2012 at 12:35 PM, michal.warecki wrote: > Hi, > > I am a student and think about competing in the Google Summer of Code this > year. I'm a big fan of open source and Camel, and I thin

Re: [DISCUSS] Camel Spring Batch

Hi, For google project you can even look at this option, integrating with Bloomberg Market Data api. Many companies i.e hedge fund, Investment bank, High frequency trading firms will find this Bloomberg market api component with camel very useful !. The challenge will be understanding how to manag

Spring 3.1 upgrade timeline

Hi Camel riders, I am curious to know if Camel version 2.10.0 support Spring 3.1 or will it be in 3.0 (if that is the version after 2.10.0) ? I noticed there is a JIRA for Spring upgrade but it is not clear in which version it will be upgraded. https://issues.apache.org/jira/browse/CAMEL-4778

Re: [DISCUSS] How to improve the documentation of new functionality (for older releases)

I'm not sure that needs to be done -- the documentation should be relevant for the latest version of each branch (2nd digit) of Camel. So in your example below, the documentation should just state what is available in the latest versions of each branch--i.e., 2.7.5, 2.8.3, 2.9.1, etc.--and not

Re: [DISCUSS] How to improve the documentation of new functionality (for older releases)

Christian, Putting the content in an SCM will not really solve the problem. The first thing that needs to be answered is: how do you want to present the version specific information to the users? - the way it is now - provide tables for all of the version specific stuff - use versioned s

Re: svn commit: r1241501 - /camel/branches/camel-2.9.x/camel-core/src/main/java/org/apache/camel/api/management/mbean/ManagedPerformanceCounterMBean.java

Hi Babak, You don't have to revert the change. It could be more easy by using "svnmerge.py block -rREVISION_NUMBER" to block the version that you already merged. On Tue Feb 7 23:49:57 2012, bvah...@apache.org wrote: Author: bvahdat Date: Tue Feb 7 15:49:57 2012 New Revision: 1241501 URL: h

Re: Requesting wiki karma

Thanks, done. Hadrian On 02/07/2012 03:31 AM, Mitko Kolev wrote: Hi Hadrian, that was really amusing :) Now the addresses should be in sync :) Thanks and regards, Mitko Hi Mitko, Thanks for your interest in Camel and willingness to contribute. The email address associated with the w

Re: CI-Server profiles for Apache Camel

Thanks Dan, Hadrian On 02/07/2012 09:25 AM, Daniel Kulp wrote: On Tuesday, February 07, 2012 6:07:44 AM Babak Vahdat wrote: Hi Is anything to be done regarding the following points: - We don't own Camel.2.9.x& Camel.2.9.x.fulltest profiles on Jenkins. Added. - Shouldn't we remove Camel

[DISCUSS] Camel 2.9.1 Release

There are some 65 issues resolved for 2.9.1 and 6 weeks since the 2.9.0 release. I am planning on releasing 2.9.1 in a week or so. Thoughts? -- Hadrian Zbarcea Principal Software Architect Talend, Inc http://coders.talend.com/ http://camelbot.blogspot.com/

Re: CI-Server profiles for Apache Camel

On Tuesday, February 07, 2012 6:07:44 AM Babak Vahdat wrote: > Hi > > Is anything to be done regarding the following points: > > - We don't own Camel.2.9.x & Camel.2.9.x.fulltest profiles on Jenkins. Added. > - Shouldn't we remove Camel.2.7.x and Camel.2.7.x.fulltest profiles, AFAIK > 2.7.x

CI-Server profiles for Apache Camel

Hi Is anything to be done regarding the following points: - We don't own Camel.2.9.x & Camel.2.9.x.fulltest profiles on Jenkins. - Shouldn't we remove Camel.2.7.x and Camel.2.7.x.fulltest profiles, AFAIK 2.7.x is not supported anymore. - On Wiki I didn't find any page saying which versions are c

Non-extensible third-party class requires copied code from ASL licensed source

I'm working on CAMEL-4987 [1] and I have a situation where a class from Spring cannot be extended. The class in question, AbstractTestNGSpringContextTests [2], is a part of the Spring Test library. It uses an annotation that precludes extension in this use case. The Spring documentation indicate

Message Correlation in Request/Reply

Hi I recently encountered an interesting problem, where I needed to set an output message via an enricher with a dynamic URI or an aggregator. The StackOverflow link below explains the situation. http://stackoverflow.com/questions/9171291/camel-request-reply-correlation I discussed this with "cs

Re: Requesting wiki karma

Hi Hadrian, that was really amusing :) Now the addresses should be in sync :) Thanks and regards, Mitko > Hi Mitko, > > Thanks for your interest in Camel and willingness to contribute. The > email address associated with the wiki and the icla don't match. You > sent this email from yet a