There is a reason, yes. UIMA defines a special code style. The checked in files
configure Eclipse to set up that code style. I have a large number of projects
in my workspace with different code styles and want to avoid checking in with 
the
wrong style.

What do you need the svn:eol-style to be set to?

Mind, I also have the dirty-on-checkout problem with the launch configurations 
in

uimaj-examples/src/main/run_configuration

but rather than just changing the eol style, Eclipse rewrites the whole file,
reordering entries, removing the license header, etc.

-- Richard

On 27.09.2013, at 20:46, Marshall Schor <[email protected]> wrote:

> My svn checkout in Eclpse of uimaFIT is showing some projects (not all) seem 
> to
> have some of the Eclipse project's ".settings" files checked into SVN.
> 
> Furthermore, the files that are checked in do not have the svn:eol-style 
> ignore set.
> 
> The result is that on my "windows" system, these files show as having outgoing
> changes (consisting of changing the line endings to windows style).
> 
> Most (essentially all) of our projects do not check in eclipse settings 
> files. 
> Is there a need to have some of the uimaFIT projects have these checked in?  
> If
> not, I'd like to remove these to avoid spurious empty "change" activity.
> 
> -Marshall

Reply via email to