Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 47581 invoked from network); 7 May 2005 13:41:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 7 May 2005 13:41:20 -0000 Received: (qmail 53227 invoked by uid 500); 7 May 2005 13:44:14 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 53152 invoked by uid 500); 7 May 2005 13:44:14 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 53136 invoked by uid 99); 7 May 2005 13:44:13 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from ns3.wkwyw.net (HELO ns3.wkwyw.net) (217.199.181.91) by apache.org (qpsmtpd/0.28) with SMTP; Sat, 07 May 2005 06:44:13 -0700 Received: (qmail 29209 invoked from network); 7 May 2005 13:41:19 -0000 Received: from 82-69-78-226.dsl.in-addr.zen.co.uk (HELO ?192.168.0.4?) (82.69.78.226) by ns3.wkwyw.net with SMTP; 7 May 2005 13:41:19 -0000 Message-ID: <427CC57A.7040202@apache.org> Date: Sat, 07 May 2005 14:41:14 +0100 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: SVN Inconsitent Line Endings References: <41D826A1.8050805@apache.org> <41D8710B.4050607@apache.org> <20050505070812.GA2596@igg.indexgeo.com.au> <427B8641.7020705@apache.org> <20050507033250.GF4535@igg.indexgeo.com.au> In-Reply-To: <20050507033250.GF4535@igg.indexgeo.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N David Crossley wrote: > Ross Gardler wrote: > >>David Crossley wrote: >> >>>I presume that this does not happen when you do 'forrest' to >>>build the plugin's docs, rather than doing 'ant docs'. >> >>I had also assumed that, however it turns our to be incorrect. >> >>In fact doing "forrest site" on any site, including site-author, results >>in the same error. >> >>I can only assume that it has not raised it's head before because I have >>not been the first person to commit generated sites to SVN with the eol >>settings set to "native". > > > Sorry, i can't parse that. Too many "nots". :-) > > All text files should have line-endings appropriate for the local system > OS and should always be 'svn propset svn:eol-style native'. Sorry, I'll try again, but I'll try by asking a couple of questions rather than stating what I think the problem might be. Has anyone built a site using Forrest on Windows and then been the first to commit it to SVN? Do we know for sure that the Ant SVN tasks pick up the SVN config info? >>Given the above observation that the XSL generated comments ahve >>different line endings to other XSL generated files I can only assume it >>is something to do with the XSLT parser. > > > What happens when you do a simple test with Xalan on the commandline. Not sure, I'll do that soon. >>For now I have put a workaround in place in the buildfile (uses an ant >>task to fix the line endings). I'll also place an issue on the issue >>tracker to remind us of this. > > > I saw that. However i couldn't understand why it was converting > them to UNIX line-endings regardless of which OS the user is on. > Do we need to detect the OS? I converted to UNIX more out of habit than design. But it works for me and I'm on Windows so I'm happy. > I have not heard of this problem before. At Cocoon and Incubator, > people on various operating systems generate the website and commit > the result to SVN, with no problems. Yes, but they don't do what we are doing with docs generated by Forrest and then imported into SVN by ant tasks. Ross