Re: Camel 2.5 - Starts to look good for a relese

Okay all is set and we are ready for the 2.5 release. Hadrian take it away. On Tue, Oct 12, 2010 at 4:50 PM, Claus Ibsen wrote: > Hi > > Last minute ticket which James Strachan would love to get in > https://issues.apache.org/activemq/browse/CAMEL-3222 > > I am running full

Re: svn commit: r1021642 - in /camel/trunk/camel-core/src: main/java/org/apache/camel/model/ThreadsDefinition.java test/java/org/apache/camel/processor/ThreadsZeroInCoreAndMaxPoolTest.java

ws Exception { >>                  from("direct:start") >> -                    // will use a a custom thread pool with 5 in core and >> 10 as max >> -                    .threads(5, 10) >> +                    // will use a a custom thread p

Re: svn commit: r1022017 - /camel/trunk/camel-core/src/main/java/org/apache/camel/impl/DefaultExecutorServiceStrategy.java

{ > +            corePoolSize = 1; > +        } > + >         ExecutorService answer = > ExecutorServiceHelper.newThreadPool(threadNamePattern, name, corePoolSize, > maxPoolSize, keepAliveTime, >                                                                       > timeUnit, maxQueueSize,

Re: Camel 2.5 - Starts to look good for a relese

Hadrian, how is the 2.5 release going? On Tue, Oct 12, 2010 at 9:53 PM, Henryk Konsek wrote: > When you release camel-apache, I'll release camel-extra 2.5 . > > On Tue, Oct 12, 2010 at 9:24 PM, Claus Ibsen wrote: >> Okay all is set and we are ready for the 2.5 release. &

Re: Camel 2.5 - Starts to look good for a relese

On 10/14/10 11:30 AM, Hadrian Zbarcea wrote: >>> Still a few errors to sort out. I got a couple of failures in jetty, the >>> eclipse goal is not working properly either yet in spring and blueprint. >>> Hadrian >>> >>> On Oct 13, 2010, at 5:56 PM, Clau

Re: Deprecated......

n various units >  * >  * @version $Revision$ >  * @deprecated will be removed in Camel 2.5 >  */ > @Deprecated > > in a file that is still there mere hours before (or maybe after) Camel 2.5 is > supposed to be released? > > :-) > > > -- > Daniel Kulp > dk.

Re: Deprecated......

may do this when JDK8 comes out with JodaTime built-in :) On Thu, Oct 14, 2010 at 9:04 PM, Claus Ibsen wrote: > On Thu, Oct 14, 2010 at 8:43 PM, Daniel Kulp wrote: >> >> Anyone else find it funny to see a comment like: >> > > No not really. > > The important thin

Re: Camel 2.5 - Starts to look good for a relese (for real)

st because it runs doesn't mean it works.   The generated projects >>>>>> cannot be imported into Eclipse.   You should not be pointing to src >>>>>> dirs outside the maven project.   That breaks all kinds of things, >>>>>> eclipse being one of th

Re: Additional fields on the components.

gt; > Thoughts? > I would much rather have a single page with "OSGi known issues" or what an appropriate title would be. This would keep maintenance much easier, as we dont have to update all 70+ components, 20+ data formats, 15+ languages, and what else we got about OSGi tests and wha

Re: [camel-extra][smooks] Dependencies only in mirror repo

a very simple project. And moving forward you should use the native Camel support from the official Smooks project instead. Its much more power full. > On Tue, Oct 12, 2010 at 6:00 AM, Claus Ibsen wrote: >> The Smooks framework itself will integrate with Camel in their next release >> h

[DISCUSS] - Easier Camel route debugging from Camel Test Kit

teBuilder createRouteBuilder() throws Exception { return new RouteBuilder() { @Override public void configure() throws Exception { // this is the route we want to debug from("direct:start") .to("mock:a"

Re: Syslog.

@opennms.org > They that can give up essential liberty to purchase a little temporary > safety, deserve neither liberty nor safety. > Benjamin Franklin, Historical Review of Pennsylvania, 1759 > > > > > > -- Claus Ibsen Apache Camel Committer Author of Cam

Re: [VOTE] Release Apache Camel 2.5.0

-001/org/apache/camel/apache-camel/2.5.0/ > > Please review and vote to approve this release binary. Your vote counts! > > [ ] +1 Release the binary as Apache Camel 2.5.0 > [ ] -1 Veto the release (provide specific comments) > Vote is open for 72 hours. > > Here's

Re: svn commit: r1023715 - in /camel/trunk/components: camel-cxf/src/test/java/org/apache/camel/component/cxf/CXFGreeterRouterTest.java camel-jms/src/test/java/org/apache/camel/component/jms/bind/JmsM

"body", "SomeBody", bean.getBody()); > > -        Map headers = bean.getHeaders(); > -        assertNotNull("No headers!", headers); > -        assertEquals("foo header", "bar", headers.get("foo")); > +        Map beanHeaders

Re: [DISCUSS] - Easier Camel route debugging from Camel Test Kit

tc. But for starters we could maybe shot for the filter and having debug fluent builder. Then later we can add nice builder methods to define fine grained when to invoke it. Having the filter allows you to let it filter out the noise. > > > On 16 October 2010 14:26, Claus Ibsen wrote:

Re: [VOTE] Release Apache Camel 2.5.0

an option to disable loading type converters on startup. > -- > View this message in context: > http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-5-0-tp3216830p3217639.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen Apache

Re: [DISCUSS] Some thoughts about the architecture of camel

architecure and rules like above. Then the next step is to >> assign each package of core to one of the basic parts. Then the next step is >> to resolve cycles between the parts. >> >> What do you think about these ideas? >> >> Thanks >> >> Christi

Re: [DISCUSS] Some thoughts about the architecture of camel

On Tue, Oct 19, 2010 at 6:40 AM, Johan Edstrom wrote: > Since you did not get your Coffee :) > Would you mind putting the hindrances up to the mere mortals? > What do you mean? > > On Oct 18, 2010, at 10:23 PM, Claus Ibsen wrote: > >> Hi >> >> I think the i

Re: [DISCUSS] Some thoughts about the architecture of camel

18, 2010, at 10:42 PM, Claus Ibsen wrote: > >> On Tue, Oct 19, 2010 at 6:40 AM, Johan Edstrom wrote: >>> Since you did not get your Coffee :) >>> Would you mind putting the hindrances up to the mere mortals? >>> >> >> What do you mean? >> >>

Re: [DISCUSS] Some thoughts about the architecture of camel

can't make them easily run on some CI servers we can at least run them locally to keep an eye on it. > > Am 19.10.10 06:23, schrieb Claus Ibsen: >> >> Hi >> >> I think the idea is really great, but I think the timing for this is >> *not* the right spot.

Re: [VOTE] Release Apache Camel 2.5.0

; Sitz der Gesellschaft: Karlsruhe >> Handelsregister: Amtsgericht Mannheim - HRB 108550 >> Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck >> Geschäftsführer: Jochen Adenau, Hans-Günther Meier >> >> >> > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus

Re: [DISCUSS] Some thoughts about the architecture of camel

On Tue, Oct 19, 2010 at 1:47 PM, Daniel Kulp wrote: > On Tuesday 19 October 2010 12:23:27 am Claus Ibsen wrote: >> Hi >> >> I think the idea is really great, but I think the timing for this is >> *not* the right spot. > > > Why not? > >> >> An

Re: [VOTE] Release Apache Camel 2.5.0

drian > > On Oct 18, 2010, at 5:39 PM, Christian Müller wrote: > >> Hello Hadrian! >> >> I cannot download the artifacts from the staging repository, because I >> receive a "Bad Gateway". Do you canceled the vote already? >> >> Regards, &

Re: [DISCUSS] Some thoughts about the architecture of camel

spatching > > Tel : +49-(0)721-63-15482 > > EnBW Systeme Infrastruktur Support GmbH > Sitz der Gesellschaft: Karlsruhe > Handelsregister: Amtsgericht Mannheim ­ HRB 108550 > Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck > Geschäftsführer: Jochen Adenau, Hans-Günther Meier >

Re: Some thoughts about the architecture of camel

, impl >>> >>> What benefits do you see for end users and component developers having >>> to depend on at least 3 jars rather than one? >>> >>> One of the reasons I like camel-core as it is; its nice and simple and >>> just works. You can build & r

Re: [DISCUSS] - Easier Camel route debugging from Camel Test Kit

n the >>> flow for the original message. Then it'd be much easier to 'step >>> through' camel routes. >>> Yeah of course just let the IDE do the conditional breakpoints. We should just make it easier for it having the short name and a few other infos eas

Re: [VOTE] Release Apache Camel 2.5.0

ith >> 26MB really big - compared to the unix source distribution with 10MB... >> >> christian-muellers-macbook-pro:apache-camel-2.5.0-src-zip muellerc$ ls -1 | >> wc -l >>    8763 >> >> I think this is more than only ugly. I'm not putting a -1 in yet,

Re: [VOTE] Release Apache Camel 2.5.0

ove this release binary. Your vote counts! >> >> [ ] +1 Release the binary as Apache Camel 2.5.0 >> [ ] -1 Veto the release (provide specific comments) >> Vote is open for 72 hours. >> >> Here's my +1 >> >> Hadrian > > > > > -- > Ch

Re: Design advice. - Syslog DataFormat.

*= 10; >            hour += Character.digit(charFound, 10); >        } > >        int minute = 0; >        while (Character.isDigit(charFound = (char) (byteBuffer.get() & > 0xff))) { >            minute *= 10; >            minute += Character.digit(charFound, 10); >        } >

Re: Design advice. - Syslog DataFormat.

her the data and build the message. I assume Netty is almost the same approach. The lead on Netty was also lead on Mina. > /je > On Oct 20, 2010, at 3:40 AM, Claus Ibsen wrote: > >> We usually add placeholders for popular data formats in the DSL. >> >> So you can do mar

Re: Design advice. - Syslog DataFormat.

ms with the BSD > syslog spec, i.e it is 1024 > bytes long and that is it. > > I'll look into the Netty side and see if I can't make a similar packet codec > for it. > > /je > On Oct 20, 2010, at 3:40 AM, Claus Ibsen wrote: > >> We usually add placeholde

Re: [RESULT][VOTE] Release Apache Camel 2.5.0

orgapachecamel-001/org/apache/camel/apache-camel/2.5.0/ >> >> Please review and vote to approve this release binary. Your vote counts! >> >> [ ] +1 Release the binary as Apache Camel 2.5.0 >> [ ] -1 Veto the release (provide specific comments) >> Vote is open f

Re: Signed ICLA

in the >> Apache Software Foundation records. >> >> If you have been voted in as a committer, please advise the project PMC that >> your ICLA has been filed. >> >> Warm Regards, >> >> Craig L Russell >> Secretary, Apache Software

Re: Signed ICLA

On Sun, Oct 24, 2010 at 12:27 PM, Richard Kettelerij wrote: > Claus, I've tried logging in/out but I can't edit pages or add new ones. > Try again, I have upgraded you once step further. > On Sun, Oct 24, 2010 at 12:11 PM, Claus Ibsen wrote: > >> Hi >> >&

Re: [RESULT][VOTE] Release Apache Camel 2.5.0

us posted on the progress of the release. > Cheers, > Hadrian > > > On Oct 23, 2010, at 3:47 AM, Claus Ibsen wrote: > >> Hi >> >> On Wed, Oct 20, 2010 at 4:11 PM, Hadrian Zbarcea wrote: >>> This vote did not pass. We need to cleanup the builds a bit

Re: [RESULT][VOTE] Release Apache Camel 2.5.0

d + bad news :) -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus

Re: [DISCUSS] - Easier Camel route debugging from Camel Test Kit

s release. Also it gives us a bit time to thinker about the API when we got a couple of months to use it before we do the 2.6 release. > Thanks, > Christian > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http

Re: [VOTE] Release Apache Camel 2.5.0

facts, the .formatted files are no longer > there, signatures look ok. > Please review and vote to approve this release binary. Your vote counts! > > [ ] +1 Release the binary as Apache Camel 2.5.0 > [ ] -1 Veto the release (provide specific comments) > Vote is open for

Re: Do you provide support or consulting?

- > View this message in context: > http://camel.465427.n5.nabble.com/Do-you-provide-support-or-consulting-tp3237598p3237598.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http:

HEADS UP - Removed some old cruff in root pom.xml

-2.1.12 -2.1 - 1.6 -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: Camel 2.5.0 released

operties from the > Registry using the ref: prefix. > > > Download [4] Camel now and enjoy the ride! > Hadrian > > [1] http://camel.apache.org/ > [2] http://camel.apache.org/2010/10/31/camel-250-released.html > [3] http://camel.apache.org/camel-250-release

Re: [JSch-users] ANNOUNCE: JSch 0.1.44

nd Publish to Ovi Store > http://p.sf.net/sfu/nokia-dev2dev > ___ > JSch-users mailing list > jsch-us...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jsch-users > -- Claus Ibsen - FuseSource Ema

Re: ftp2 - idempotent feature

omponent apply for ftp2. > I have tried using idempotent=true in my ftp connection uri but all files > are still being processed. > Can someone tell me if I am missing something? > Thanks, > > -- > Deepti Bhogle > Software Engineer > -- Claus Ibsen -

Re: [DISCUSS] CXF 2.3 upgrade in Camel 2.6?

xed and get them into 2.3.1 which I'd > like to do later this month. > > The camel 3.0 version in Q1 is still not finalized/settled, so I wouldn't use > that as part of the decision point. > > Dan > > >> >> Thanks, >> Willem and William >

Re: Camel 2.5 - Starts to look good for a relese

ally release:prepare doesn't work and I need to get > deeper into the plugin to debug why this happens :) > > I'll let you know when I figure it out and release 2.5. > Ah great. Yeah good luck with Maven. When it works its great. But when it don't you are sometimes

Re: Failing unit tests of spring-ws component in CI.

        > > > It's a snippet from the pom.xml included in my original patch (CAMEL-3105). > Perhaps a committer (Claus?) can add this (in the parent pom). > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: Camel test coverage in Hudson/Sonar

kes a fair bit of time to run. And when there is code coverage there is a little overhead as well. We run it once in a while locally to detect gaps in the most important components. > Regards, > Richard > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: htt

Re: helping out with the Web site

ally refresh. If includes or navigation is >> changed you usually have to wait for an administrator to run >> AutoExport on the entire site... >> >> >> -- >> James >> --- >> FuseSource >> Email: ja...@fusesource.com >> Web: http://fusesourc

Re: [jira] Created: (CAMEL-3325) camel-jmx: Auto creation of a monitor bean via endpoint properties

o compare against the >> attribute value | >> >> Other considerations >> * If the mbeanserver is remote, then the JMXRemote library or similar >> solution is required to register the monitor bean >> * name of the monitor bean should be derived from the observed object >> * if the observed bean is unregistered then the route should send some >> notification or exception through its route to signal the processors >> >> >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >> >> > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: LDAP Component

ly. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any attachment > and all copies and inform the sender. Thank you. > > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: svn commit: r1034252 - /camel/trunk/apache-camel/pom.xml

                  > -                     > -                      ${project.groupId} > -                      camel-spring > -                      javadoc > -                      ${project.version} > -                     > -                   > -                 > -               > -             > -           > -         > -       > -     > -   > - >   > > > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: svn commit: r1034252 - /camel/trunk/apache-camel/pom.xml

dated. > Cheers, > Hadrian > > On Nov 12, 2010, at 9:26 AM, Claus Ibsen wrote: > >> Hi Hadrian >> >> Can you elaborate a bit on this? The release profile is removed. >> What do you mean by apache-release is used? >> >> According to the release guide >

Re: LDAP Component

722072 > Persönlich haftender Gesellschafter: Logica Deutschland Verwaltungs GmbH > Geschäftsführer: Torsten Straß (Vors.) | Steven Blythe | Dr. Markus Feidicker > | Eric Guyot | Olaf Scholz | Oliver Starzonek | Dr. Alexander Wurdack > Handelsregister: AG Stuttgart HRB 724084 > > ___

Re: Any interest in a Drools-based dynamic router?

ngs out this week and would welcome any feedback, either > proposed design or nifty features. > -- > View this message in context: > http://camel.465427.n5.nabble.com/Any-interest-in-a-Drools-based-dynamic-router-tp3265110p3265110.html > Sent from the Camel Development ma

Re: Social Network Feed Component

ng if it's worth splitting the base Feed* stuff off into >> another module, or renaming camel-atom to camel-feeds and putting my >> code in there, or just creating a brand new module that happens to >> have a dependency on camel-atom. >> >> Thoughts? >>

Re: Migrating activemq JIRA contents to https://issues.apache.org/jira

tters on Apache Camel. The following is committers (we have more, but those are the ones I could easily spot) - James Strachan - Ashwin Karpe - Christian Mueller - Christian Schneider - Claus Ibsen - Gert Vanthiensen - Hadrian Zbarcea - Jonathan Anstey - Martin Krasser - Stan Lewis - Willem Jiang

Re: svn commit: r1042087 - in /camel/trunk: components/camel-atom/ components/camel-blueprint/ components/camel-csv/ components/camel-ftp/ components/camel-quartz/ components/camel-script/ components/

        > -          true > -         > -         > -          false > -         > -       > -       > -       > -        jboss > -          Jboss Repository > -          http://repository.jboss.org/nexus/content/groups/public/ > -           > -            true > -           > -           > -            false > -           > -       > -       > -       > -        spring-milestone > -        Spring Portfolio Milestone Repository > -         > http://s3.amazonaws.com/maven.springframework.org/milestone > -         > -          true > -         > -         > -          false > -         > -       > - > -       > -       > -        java.net.m2 > -        Java.net Repository for Maven > -        http://download.java.net/maven/2/ > -        default > -       > -     > >   > > Modified: camel/trunk/tests/camel-itest-karaf/pom.xml > URL: > http://svn.apache.org/viewvc/camel/trunk/tests/camel-itest-karaf/pom.xml?rev=1042087&r1=1042086&r2=1042087&view=diff > == > --- camel/trunk/tests/camel-itest-karaf/pom.xml (original) > +++ camel/trunk/tests/camel-itest-karaf/pom.xml Sat Dec  4 02:54:39 2010 > @@ -31,13 +31,6 @@ >   Camel :: Karaf Integration Tests >   Performs Karaf compliance integration tests > > -   > -     > -      biz.aQute > -      http://www.aqute.biz/repo > -     > -   > - >   >     >       org.ops4j.pax.exam > > Modified: camel/trunk/tests/camel-itest-osgi/pom.xml > URL: > http://svn.apache.org/viewvc/camel/trunk/tests/camel-itest-osgi/pom.xml?rev=1042087&r1=1042086&r2=1042087&view=diff > == > --- camel/trunk/tests/camel-itest-osgi/pom.xml (original) > +++ camel/trunk/tests/camel-itest-osgi/pom.xml Sat Dec  4 02:54:39 2010 > @@ -34,10 +34,6 @@ > >   >     > -      biz.aQute > -      http://www.aqute.biz/repo > -     > -     >       hapi >       HAPI Maven Repository >       http://hl7api.sourceforge.net/m2/ > > > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: svn commit: r1043407 - in /camel/trunk: components/camel-blueprint/src/main/java/org/apache/camel/blueprint/ components/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/ components

On Fri, Dec 10, 2010 at 6:05 AM, Claus Ibsen wrote: > On Fri, Dec 10, 2010 at 12:46 AM, Guillaume Nodet wrote: >> I actually did, and it seems to work for me. What kind of errors do you have >> ? >> > > For example fusesource CI :) > http://ci.fusesource.com/hud

Re: [VOTE] Release Apache Camel 1.6.4

rgapachecamel-003/org/apache/camel/apache-camel/1.6.4/ >> >> Please review and vote to approve this binary as the final 1.6.4 >> maintenance release. Your vote counts! >> >> [ ] +1 Release the binary as Apache Camel 1.6.4 >> [ ] -1 Veto the relea

Apache Camel - Update documentation for release procedure

this as part of doing the next release, such as Camel 2.6? Then at the same time you do the release, you update the documentation. That way we get the documentation updated based on actual procedure you do. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http

Johan, it happens for all committers

except crappy and mysterious issues with osgi, but that's another story for all of us). -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: Johan, it happens for all committers

or a smile. > I made the change after hunting an NPE when upgrading code from an > older Camel release. > Ah nice maybe you can can provide more details and we can either add a note in a release note or get the NPE fixed it ifs a valid bug. > > > On Dec 17, 2010, at 11:15

Re: Johan, it happens for all committers

PollerEndpoint ep = (DatasourcePollerEndpoint) > camelContext.getEndpoint(from.getUri()); > > This behavior was working up until Revision #954840 Committed by ningjiang > 6/15/10 5:44 AM CAMEL-2811 the routeContext should be independent on > CamelContext, > I'm guessing sin

Compilation error on trunk on windows on Apache Jenkins

.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) -- Claus Ibsen -

Re: Compilation error on trunk on windows on Apache Jenkins

"amd64", family: "windows" > > Christian > > > Am 11.09.2011 12:44, schrieb Christian Schneider: >> >> Hi Claus, >> >> I also could not reproduce the error. Will send the details of my work >> machine later. >> I guess the most proba

Re: Compilation error on trunk on windows on Apache Jenkins

Okay the patch seems to work. Apache CI server can now compile and test camel-core. Its currently running a full test https://builds.apache.org/job/Camel.trunk.fulltest.windows/15/console On Mon, Sep 12, 2011 at 7:59 AM, Claus Ibsen wrote: > Thanks > > I committed a potential fix and

Re: [RESULT][VOTE] Release Apache Camel 2.8.1

> counts! >> >> [ ] +1 Release the binary as Apache Camel 2.8.1 >> [ ] -1 Veto the release (provide specific comments) >> Vote is open for at least 72 hours. >> >> Here's my +1 >> Hadrian >> >> [1] >> https://issues.apache.o

Re: svn commit: r1170077 - in /camel/trunk: components/camel-jpa/pom.xml components/camel-jpa/src/main/java/org/apache/camel/component/jpa/JpaConsumer.java parent/pom.xml platforms/karaf/features/src/

27;> >> -> dependency="true">mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.java-persistence-api-1.1.1/${servicemix-specs-version} >> +> dependency="true">mvn:org.apache.geronimo.specs/geronimo-jpa_2.0_spec/${geronimo-

Re: svn commit: r1170077 - in /camel/trunk: components/camel-jpa/pom.xml components/camel-jpa/src/main/java/org/apache/camel/component/jpa/JpaConsumer.java parent/pom.xml platforms/karaf/features/src/

: Thu Sep 15 10:44:17 CEST 2011 [INFO] Final Memory: 11M/30M [INFO] -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http

[ANNOUNCE] - Apache Camel 2.8.1 Released

available for download from the Apache site [1]. [1] - http://camel.apache.org/download [2] - http://camel.apache.org/camel-281-release.html -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http

Re: Apache ICLA sent

Tombs, > > This message acknowledges receipt of your ICLA, which has been filed in > the Apache Software Foundation records. > > If you have been voted in as a committer, please advise the project PMC > that your ICLA has been filed. > > Warm Regards, &g

Camel 2.8.2 - Reason for the many backports?

s you lose this, and cannot keep the documentation <-> source code in sync. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: Camel 2.8.2 - Reason for the many backports?

gap from 2.8.0, 2.8.1 to 2.8.2 is now very big. This is not desireable. On Tue, Sep 20, 2011 at 8:11 AM, Claus Ibsen wrote: > Hi > > Dan what is the reason why you backport so many commits to 2.8.2 from 2.9? > > The "problem" is that its a lot of new features, non trivia

Re: Camel netty encode bug

-- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-netty-encode-bug-tp4825369p4825369.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: Camel 2.8.2 - Reason for the many backports?

I get it right? Is there a particular commit that triggered this >>>>> question, or is more the principle? >>>>> >>>>> Hadrian >>>>> >>>>> On 09/21/2011 01:36 AM, Rob Davies wrote: >>>>>> Dan it admirabl

Re: Camel 2.8.2 - Reason for the many backports?

t;>> >>>>>> Rob seems to imply that he trusts 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. >>>>>> >>

Re: Camel 2.8.2 - Reason for the many backports?

e 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 D

Merging to Camel 2.7 branch issue

/camel/branches/camel-2.7.x Repository Root: https://svn.apache.org/repos/asf So when I run svnmerge.py merge -r 1124595 It cannot merge that fix to the 2.7 branch. I know some of you guys are svnmerge.py experts, and maybe can check it out. -- Claus Ibsen - FuseSource Email: cib

Re: Merging to Camel 2.7 branch issue

> fix manually for you... not sure the best way to fix this up... > Thanks Jon. Yeah that seems messed up. We should be looking into backport some of the important issues we have found recently which may also affect the 2.7 branch. > On Thu, Sep 22, 2011 at 9:29 AM, Claus Ibsen wrote

Re: Merging to Camel 2.7 branch issue

.py rollback -M -r 1124595" to mark it as > not integrated and then rerun the "svnmerge.py merge". > I guess we can leave it as is? And chances are we are merging recent bug fixes back to the 2.7 branch? > Dan > > > > >> On Thu, Sep 22, 2011 at 9:

Re: Camel 2.8.2 - Reason for the many backports?

to find an older svnmerge.py file that dont fail at the end. If anyone got a .py file working, then feel free to attach on a mail and send to me, or this @dev. On Thu, Sep 22, 2011 at 3:34 PM, Daniel Kulp wrote: > On Thursday, September 22, 2011 7:45:28 AM Claus Ibsen wrote: >> On We

[DISCUSS] - Trunk as Camel 3.0

nk such as: new components, and other improvements, new features, which we think is worthwhile and that the community would like to have in the Camel 2.9 release. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews

Re: [DISCUSS] - Trunk as Camel 3.0

ficially. We can then split up the core into smaller pieces, and have a camel-api JAR (or whatever a good name could be ) which has the end user API. Then from Camel 3.0.0 onwards we have a much better platform to keep a good and stable API for the large and growing Camel community. > Chr

Re: Camel 2.8.2 - Reason for the many backports?

7b277 On Thu, Sep 22, 2011 at 7:02 PM, Daniel Kulp wrote: > On Thursday, September 22, 2011 6:44:42 PM Claus Ibsen wrote: >> Hi >> >> I gave the DoMerges tool a try and it worked fine. >> >> However as my svnmerge.py python script causes some UTF-8 error after &

Re: Camel 2.8.2 - Reason for the many backports?

t;> > >> >> > If anyone got a .py file working, then feel free to attach on a mail >> >> > and send to me, or this @dev. >> >> >> >> >> >> I've attached mine. What kind of error were you getting? D

Re: Camel 2.8.2 - Reason for the many backports?

>> Also how to do it with the mentioned Java/Python scripts, as we have it done >> with our release step-by-step guide. I didn't know these scripts and nobody >> told me about their existence. I was not able to find a WIKI page about it >> (with my mobile phone ;-) ). I could imagine, I'm not the o

Re: Camel 2.8.2 - Reason for the many backports?

rt. For example if we have a known work-around it could be better to notice the workaround in the release notes for that given release. > 3) Still not clear why we backport many issues to 2.8.2 and not to 2.7.4. > > I stess this to make it clear for everybody, document it and to provide

Re: Camel 2.8.2 - Reason for the many backports?

t; > We should backport as much as we can to 2.7.x while it is maintained. I > think it's just a matter of finding the time to do it. > > >> I stess this to make it clear for everybody, document it and to provide a >> better mentoring for new committers. > &g

Re: Camel 2.8.2 - Reason for the many backports?

d svmerge.py file may have an issue. I have switched to use the copy from Dan. I had trouble today backporting a fix to the 2.7 branch. Could anyone try to backport CAMEL-4487? The rev number in the 2.8 branch is: 1175323 CAMEL-4487 is a low-risk, minor bug fix, that would be safe to backport to t

Re: [DISCUSS] - Trunk as Camel 3.0

el 2.9 as the Camel 3.0-m1. When we developed >>>>> Camel 2.0, we actual did three mile stone release to fill the gap of >>>>> the API >>>>> change. >>>>> For the user who want to do some release just after Camel 3.0 RC is >>>>> out, >>>>> he can keep using Camel 3.0 mile stone release. >>>>> For the user who just want use the stable Camel 2.x, he can chose Camel >>>>> 2.8.x, as we already did a lot of merge of on the Camel 2.8.x branch. >>>>> >>>>> Camel 3.0 Mx can tell the user what API change will be made, and we can >>>>> removed the @Deprecates API when the Camel 3.0 is shaped. >>>>> >>>>> Any thoughts ? >>>> >>> >>> >>> -- >>> -- >>> Christian Schneider >>> http://www.liquid-reality.de >>> >>> Open Source Architect >>> Talend Application Integration Division http://www.talend.com >>> >>> > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: [DISCUSS] - Trunk as Camel 3.0

d hence we should do this with much more care. > Christian > > Sent from a mobile device > Am 24.09.2011 06:48 schrieb "Hadrian Zbarcea" : > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: d

Re: [DISCUSS] - Trunk as Camel 3.0

t; ** > Apache Karaf <http://karaf.apache.org/> Committer & PMC > Apache ServiceMix <http://servicemix.apache.org/>  Committer > Apache Gora <http://incubator.apache.org/gora/> Committer > * > -- Claus Ibsen - FuseSource Email: cib...@fusesource.co

Re: [DISCUSS] - Trunk as Camel 3.0

On Mon, Sep 26, 2011 at 1:29 PM, Christian Schneider wrote: > Am 26.09.2011 11:04, schrieb Claus Ibsen: >> >> See the survey we did where people comment that they want the API stable. >> http://camel.apache.org/camel-30-roadmap.html (link on top of this page) We >>

Re: [DISCUSS] - Trunk as Camel 3.0

new API? > So while there is a chance that people are hit the percentage may be small. > If we then react fast or even before 2.9.0 and provide compatibitlity for > people who report problems then I can imagine to make almost everyone happy > with 2.9.0. > > Christian >

Re: [DISCUSS] - Trunk as Camel 3.0

Camel 3.0. And keep the current 2.x as it has been for the last 2 years. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: [DISCUSS] - Trunk as Camel 3.0

On Mon, Sep 26, 2011 at 2:45 PM, Christian Schneider wrote: > Am 26.09.2011 14:02, schrieb Claus Ibsen: >> >> On Mon, Sep 26, 2011 at 1:17 PM, Christian Schneider >>  wrote: >>> >>> Yes there are probably some undocumented changes. The question is though &g

Re: [DISCUSS] - Trunk as Camel 3.0

Also because Camel 2.9.0 is *not* going to be like any other regular >> minor releases we usually do. >> >> So doing 1-2 RC releases could be a good thing for the community. >> > -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/

Re: 2.7.4/2.8.2 releases....

mmediately with a Camel 2.8.2 release.   From a > timing standpoint and such, I would expect to be able to do the Camel build on > the 11th. > > I'm more than happy to do a 2.7.4 build/release at the same time as well. > > > -- > Daniel Kulp > dk...@apache.org > http:

[FIX] - Download source links

Hi Didn't we unify the source so there is only a .zip distribution now? If so we should fix the download page to only list the link for the .zip file. -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog:

Backporting to 2.7 branch - 2 files changed

svnmerge property assigned or whatever so they get changed. Anyone know how to resolve this? Or should we just not care? -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of

<    6   7   8   9   10   11   12   13   14   15   >