FYI, with the revisions that Willem & Claus [1] have already commited the
issue seems to be resolved, so that while synchronizing with the trunk
(subclipse in eclipse) happily I see 0 outgoing-changes.
But maybe you still want to double check it.
[1] http://svn.apache.org/viewvc?view=revision&rev
On Friday, December 02, 2011 5:32:25 AM bvahdat wrote:
> @Dan,
>
> did you have a chance to give that CXF script a try?
Yea... but was getting test failures/hang that I wasn't sure if they were
related or not. It looks like the hang in camel-spring wasn't so I'll
continue checking.
Basically
@Dan,
did you have a chance to give that CXF script a try?
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/The-svn-ignore-property-isn-t-settled-down-on-trunk-tp5035110p5041830.html
Sent from the Camel Development mailing list archive at Nabble.com.
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
@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
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
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
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 (
