Mailing-List: contact uima-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: uima-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of twgoetz@gmx.de designates
 213.165.64.20 as permitted sender)
Message-ID: <48FF51DB.7010803@gmx.de>
Date: Wed, 22 Oct 2008 18:16:27 +0200
From: Thilo Goetz <twgoetz@gmx.de>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: uima-dev@incubator.apache.org
Subject: Re: [jira] Commented: (UIMA-1163) set svn:eol-style to native for
 source files in UIMA project
References: <393428048.1224690344260.JavaMail.jira@brutus>
In-Reply-To: <393428048.1224690344260.JavaMail.jira@brutus>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Ok, no problem.  I just thought maybe you were done and had forgotten to close the defect.  Thanks.

--Thilo

Marshall Schor (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/UIMA-1163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641891#action_12641891 ] 
> 
> Marshall Schor commented on UIMA-1163:
> --------------------------------------
> 
> The work is not finished.  It fell down in the priority list of things to do :-).  So - it probably should not be closed, but progress on this will likely be slow unless other hands help out.
> 
>> set svn:eol-style to native for source files in UIMA project
>> ------------------------------------------------------------
>>
>>                 Key: UIMA-1163
>>                 URL: https://issues.apache.org/jira/browse/UIMA-1163
>>             Project: UIMA
>>          Issue Type: Improvement
>>          Components: Core Java Framework
>>    Affects Versions: 2.2.2
>>            Reporter: Marshall Schor
>>            Assignee: Marshall Schor
>>            Priority: Minor
>>
>> set the svn:eol-style to native for java source files in the UIMA project.  (Other sandbox projects may also want to do similar things, and the uimaCPP project, and the site project).
>> Don't set this for scripts - the ones that are intended to run on windows probably can have either line ending style, but I think the ones that run on the various linuxes need the unix style.  This is so that extracts for builds done on a windows machine can properly build a linux distribution.
>> Don't set this for test data - some UTF-16 or UTF-8 test data may have things intentionally present that might look like line endings, but are not, and should not be disturbed by checkout.  
>