Re: Good practice - When doing pull to get latest source code updates

For what it's worth this is a little ruby script we use in our environment to update from git. stash = /Saved working directory/.match(`git stash`) unless stash.nil? puts "Local working changes have been stashed" end `git fetch` `git rebase -p` unless stash.nil?

Re: 3.0 Ideas

Just to throw out some other clean-up ideas for Camel 3.0. I came across this thread here recently [1] talking about exchange patterns and the history of camel. Now that JBI is essentially dead, does it make sense to use Camel 3.0 to cleanup unused ties back to JBI? For example, get rid of the exc

Re: [DISCUSS] Move to a pure git based repo

On Wed, Mar 27, 2013 at 1:01 PM, Hadrian Zbarcea wrote: > Would that something that sounds appealing to most? I think most of us > already use mostly git anyway. The ASF infra now offers the choice. > +1 > > Same question goes about camel-extra, I opened an issue there [1] and as > much as I di

Re: [DISCUSS] - Rename camel-redis and camel-neo4j to include spring in their name

+1 On Sat, Mar 9, 2013 at 8:06 AM, Willem jiang wrote: > It makes senses. Here is my +1. > > > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com

Re: 3.0 Ideas

oking at the JmsComponent, it takes a > > PlatformTransactionManager (i.e. Spring) not a TransactionManager (JTA). > > > > If I could use a standard transaction manager right now I'd be ok for > now. > > Eventually I'd like to be able to run without spring a

Re: 3.0 Ideas

On Wed, Feb 27, 2013 at 10:20 PM, Claus Ibsen wrote: > On Thu, Feb 28, 2013 at 1:22 AM, Chris Geer wrote: > > On Wed, Feb 27, 2013 at 5:16 PM, Guillaume Nodet > wrote: > > > >> Getting rid of spring transaction support and implementing our own > layer in > >

Re: 3.0 Ideas

o run without spring at all though. > > > On Wed, Feb 27, 2013 at 9:50 PM, Chris Geer wrote: > > > On Wednesday, February 27, 2013, Henryk Konsek wrote: > > > > > Hi Chris, > > > > > > > 1) Refactor the JMS Component to use JTA transactions inste

Re: 3.0 Ideas

CAMEL-6108 <https://issues.apache.org/jira/browse/CAMEL-6108> On Wed, Feb 27, 2013 at 1:50 PM, Chris Geer wrote: > On Wednesday, February 27, 2013, Henryk Konsek wrote: > >> Hi Chris, >> >> > 1) Refactor the JMS Component to use JTA transactions instead of Sp

Re: 3.0 Ideas

On Wednesday, February 27, 2013, Henryk Konsek wrote: > Hi Chris, > > > 1) Refactor the JMS Component to use JTA transactions instead of Spring > > Transactions. > > I'm not really sure if we need to include such kind of changes in > Camel 3 roadmap. The idea is good, but can't we just raise Jira

3.0 Ideas

I'd like to cast my vote for a couple things we'd like to see in Camel 3.0 if it can be fit in. 1) Refactor the JMS Component to use JTA transactions instead of Spring Transactions. 2) We agree with the existing idea for "JMX Naming" on the idea page. Removing the hostname from the JMX names would

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

On Wednesday, July 4, 2012, Christian Schneider wrote: > Very good idea. I have done some research: > > https://issues.apache.org/**jira/browse/LEGAL-124 > http://www.apache.org/legal/**src-headers.html#faq-**exceptions

Flatpack Component Enhancements

I'm looking to make some enhancements to the Flatpack component (JIRA tickets forthcoming) and have been doing some testing/research and have come across an odd behavior. As background, the Flatpack component will translate a fixed width or delimited file into a common DataSet object. It also provi

Patch for CAMEL-5300

I created a patch to correctly propagate errors from the flatpack component (CAMEL-5300 [1]) and attached it to the JIRA. This is my first contribution to Camel so please let me know if I missed something. Thanks, Chris [1] https://issues.apache.org/jira/browse/CAMEL-5300

Karaf 2.2.4 support in 2.9.x branch

I was going to start working on some improvements for the flatpack component but ran into an issue on the 2.9.x branch. I'm currently running 2.9.2 on Karaf 2.2.4 and it's working great. I tried to install 2.9.3-SNAPSHOT and ran into an issue with camel-karaf-commands because it depends on jline 2.

Re: [DISCUSS] - XML DSL and trimming value

On Sun, May 20, 2012 at 12:28 PM, Claus Ibsen wrote: > On Sun, May 20, 2012 at 6:01 PM, Hadrian Zbarcea > wrote: > > My vote would be for *no* auto trim. Makes things predictable and easy to > > understand. > > > > Hadrian > > > > Well yeah we should improve on this. > > What I am talking about