Re: Editing rights on confluence documentation

Hi, it's there now (ugol) On Mon, Feb 17, 2014 at 8:53 PM, Christian Müller wrote: > Have a look when your license agreement is recorded at [1] and ping us > again. You may want to check whether your mail/fax was received by the > secretary via secret...@apache.org. > > [1] http://people.apache.o

No editing rights in the Wiki anymore

Hi all, a couple of days ago I tried to fix some typos in example code on the wiki, but I can't edit pages anymore. My username is "cringe". Maybe this is related to an update of the wiki software? Carsten -- www.kopis.de

Information for Google Summer of Code 2014

Dear Members, I am a university student studying computer science at University of Colombo School of Computing, Sri Lanka . I am interested in submitting a proposal for Google Summer Of Code 2014. I am from a Java background and having few exper

Re: [VOTE] Release Apache Camel 2.11.4

+1 (nonbinding) On Mon, Feb 17, 2014 at 3:28 PM, Christian Müller wrote: > +1 > > The doc looks good. > The signatures are also good. > I upgraded an older version of Camel-in-action (rev 356) with the following > test failed: > Failed tests: > testABCGroup(camelinaction.AggregateABCGroupTest)

Re: [VOTE] Release Apache Camel 2.12.3

looking forward to this release, +1 On Mon, Feb 17, 2014 at 5:01 PM, Johan Edstrom wrote: > +1 > On Feb 17, 2014, at 2:11 PM, Christian Schneider > wrote: > >> +1 >> >> Christian >> >> Am 16.02.2014 05:16, schrieb Hadrian Zbarcea: >>> This is a vote to release Apache Camel 2.12.3, a patch relea

Re: [VOTE] Release Apache Camel 2.12.3

+1 On Feb 17, 2014, at 2:11 PM, Christian Schneider wrote: > +1 > > Christian > > Am 16.02.2014 05:16, schrieb Hadrian Zbarcea: >> This is a vote to release Apache Camel 2.12.3, a patch release coming with >> about 128 issues fixed. >> >> Release notes: >> https://issues.apache.org/jira/secu

Re: [VOTE] Release Apache Camel 2.11.4

+1 The doc looks good. The signatures are also good. I upgraded an older version of Camel-in-action (rev 356) with the following test failed: Failed tests: testABCGroup(camelinaction.AggregateABCGroupTest) testABCGroup(camelinaction.SpringAggregateABCGroupTest) testCamelCallback(camelinactio

Re: [HEADS-UP] Camel 2.12.3 and 2.11.4

Please go ahead, Willem. I'm again busy with my day job... Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642

Re: [VOTE] Release Apache Camel 2.12.3

+1 Christian Am 16.02.2014 05:16, schrieb Hadrian Zbarcea: This is a vote to release Apache Camel 2.12.3, a patch release coming with about 128 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325593 Staging repo: https://rep

Re: [VOTE] Release Apache Camel 2.11.4

+1 Christian Am 16.02.2014 05:16, schrieb Hadrian Zbarcea: This is a vote to release Apache Camel 2.11.4, a patch release coming with about 26 issues fixed. Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12325645 Staging repo: https://repo

Re: Editing rights on confluence documentation

Have a look when your license agreement is recorded at [1] and ping us again. You may want to check whether your mail/fax was received by the secretary via secret...@apache.org. [1] http://people.apache.org/committer-index.html#unlistedclas Best, Christian - Software Integration

Re: [VOTE] Release Apache Camel 2.12.3

+1 The signatures are good. The doc looks good (we only have to update the copyright year). I could upgrade Camel-in-action to Camel 2.12.3 (and CXF 2.7.10) without any issues. Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC

Re: [VOTE] Release Apache Camel 2.12.3

Did he mean that it doesn't FORCE 2.7.10? > On Feb 17, 2014, at 4:55 AM, James Carman wrote: > > How does the range from 2.6 (inclusive) to 2.9 (not inclusive) not > include 2.7.10? > > On Mon, Feb 17, 2014 at 5:06 AM, Babak Vahdat > wrote: >> Hi Willem, >> >> can you please elaborate your ex

[GitHub] camel pull request: CAMEL-7215 Stop and un-schedule jobs on route ...

GitHub user davidkeen opened a pull request: https://github.com/apache/camel/pull/98 CAMEL-7215 Stop and un-schedule jobs on route removal. Call doStop() in onRemove (as in CronScheduledRoutePolicy) so jobs are un-scheduled. You can merge this pull request into a Git repository by

Re: [VOTE] Release Apache Camel 2.11.4

I figured that's what was going on. Also, I don't think the cxf-version-range property is doing what we think it's supposed to do, perhaps. It's set to [2.6,4.0), but the ranges show up as [2.6,2.9). So, perhaps we need to investigate that? I think CAMEL-7170 can remain "fixed", since it did exa

Re: [VOTE] Release Apache Camel 2.11.4

You're right and sorry for the confusion. I don't know why, but somehow my brain treated 2.7.10 as 2.9.10! So I change my vote here to +1. Babak James Carman wrote > When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see: > > org.apache.cxf;version="[2.6,2.9)" > > In this prepared 2.11

Re: [VOTE] Release Apache Camel 2.11.4

I forgot to add, there haven't been any 2.9.x (nor 2.8.x) releases for CXF yet, so we're not disallowing anything, except 3.0.x (only a milestone release thus far), which we wanted to keep out anyway. On Mon, Feb 17, 2014 at 7:52 AM, James Carman wrote: > When I open up the META-INF/MANIFEST.MF f

Re: [VOTE] Release Apache Camel 2.12.3

How does the range from 2.6 (inclusive) to 2.9 (not inclusive) not include 2.7.10? On Mon, Feb 17, 2014 at 5:06 AM, Babak Vahdat wrote: > Hi Willem, > > can you please elaborate your explanation a bit? Currently what we've on the > 2.12.x. as well as 2.11.x branches is this: > > 2.7.10 >

Re: [VOTE] Release Apache Camel 2.11.4

When I open up the META-INF/MANIFEST.MF file in 2.11.3, I see: org.apache.cxf;version="[2.6,2.9)" In this prepared 2.11.4 candidate I see: org.apache.cxf;version="[2.6,2.9)" So, nothing appears to have changed there. If we look at the feature.xml file in this release candidate: camel-sprin

Re: [VOTE] Release Apache Camel 2.11.4

Hi James, Even if we would mark the issue as not fixed, the behaviour divergency by this release candidate @ the staging repo would be still there, that's: For the non-OSGi folks who make use of camel-cxf Camel component, we would put CXF 2.7.10 for them into the classpath but for the OSGi folks w

[Question] how to proceed for websocket

Hi Camel-team, I would like to integrate the atmosphere based websocket component to camel. I posted messages regarding this topic several times and most recent one some months ago [1]. I would like to briefly summarize the current status and propose a few options about how we can proceed. I woul

Re: [VOTE] Release Apache Camel 2.12.3

Hi Willem, can you please elaborate your explanation a bit? Currently what we've on the 2.12.x. as well as 2.11.x branches is this: 2.7.10 [2.6,2.9) Now to my understanding this should become: 2.7.10 [2.6,3) I think the current range is a problem for the OSGi folks because if e