Re: The svn:ignore property isn't settled down on trunk

2011-11-30 Thread Daniel Kulp
I have a script that I run on the CXF trunk and branches every couple of months that goes through and adds a bunch of svn:* properties on all the various files including mime types and eol style things and such. With CXF, since I run it often enough, it's not a very big diff. I expect a MAS

Re: The svn:ignore property isn't settled down on trunk

2011-11-30 Thread Hadrian Zbarcea
@Babak, I assume you know how to configure your svn client [1] and about global-ignores. I don't know what os you use, on linux you can find the config at ~/.subversion/config. Another good practice is to set the default eol-style for known file types. I use a configuration derived from the c

Re: The svn:ignore property isn't settled down on trunk

2011-11-30 Thread bvahdat
Hi Willem, Thanks a lot for that quick fix. IMHO the best would be if we could consistently overcontrol the ignore list as the following so that the rules apply for *all* of us no matter what the client we use: - for svn dummies (like me) through the svn:ignore property of each given folder belo

Re: The svn:ignore property isn't settled down on trunk

2011-11-30 Thread Willem Jiang
Hi, Just commit a quick fix for it. BTW, I'm using git[1] to work on apache camel code now, it could be more simple to avoid this issue by add a .gitignore file in the project root. [1]http://git.apache.org/ On Wed Nov 30 17:53:33 2011, bvahdat wrote: Hi Devs, That would be great if some co

Re: what's the problem with bean expression

2011-11-30 Thread Willem Jiang
Please use the us...@camel.apache.org to ask this kind of question. My comments are in the mail. On 7/23/64 4:29 AM, wow wrote: I use camel 2.8.0 with servicemix4.3. I set up a dynamic router by camel-context.xml. as follows: http://www.springframework.org/schema/beans"; xmlns:xsi="ht

Re: Camel CMIS component

2011-11-30 Thread Hadrian Zbarcea
Boday, After your review, if you consider that the code is acceptable with minor fixes, I'd suggest committing the patch *as is* and then add your fixes in a follow-up commit (unless the change is really, really minor). The reason is that the patch can that be tracked to the original author,

The svn:ignore property isn't settled down on trunk

2011-11-30 Thread bvahdat
Hi Devs, That would be great if some committer would update the svn:ignore property on the trunk (as an example camel-jclouds/target folder is considered as an outgoing-change on my IDE, or .classpath & .project by some other camel components). IMHO this would make life easier for the commiters (