Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 43439 invoked from network); 3 Mar 2006 13:34:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Mar 2006 13:34:44 -0000 Received: (qmail 78795 invoked by uid 500); 3 Mar 2006 13:35:29 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 78736 invoked by uid 500); 3 Mar 2006 13:35:28 -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 List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 78724 invoked by uid 99); 3 Mar 2006 13:35:28 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 05:35:28 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [203.121.192.8] (HELO mail.e-wire.net.au) (203.121.192.8) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Mar 2006 05:35:27 -0800 Received: from developer (myself [127.0.0.1]) by mail.e-wire.net.au (8.13.1/8.13.1) with SMTP id k23DZ0B7005232 for ; Fri, 3 Mar 2006 21:35:03 +0800 Received: from 203-121-204-130.e-wire.net.au [203.121.204.130] for mail.e-wire.net.au (HELO developer) via SMTP; Fri, 03 Mar 2006 21:35:03 +0800 Message-ID: <000401c63ec7$44c2f800$0400a8c0@developer> Reply-To: "Gav...." From: "Gav...." To: Subject: Fw: Forrestbot + SVN = mixed line-endings in HTML Date: Fri, 3 Mar 2006 21:34:59 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-BitDefender-SpamStamp: 1.1.4 049000040111AAAAAAAAAAAAAAAAAABAAAAAAAAAAAAAQAAAI X-BitDefender-Spam: No (0) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N erm, sent this 12 hours ago to user@ , never got there so posting it here. ----- Original Message ----- From: "Gav...." To: Sent: Friday, March 03, 2006 7:17 AM Subject: Re: Forrestbot + SVN = mixed line-endings in HTML > Just a passing comment that may not have relevence. > > In one of my user forums, someone who is much better at xslt than me > stated not to > use with xslt 1.0 . > > I have asked him why he thinks this, and pointed him to the XALANJ-656 > issue to > see whether he thinks it relevent or not in this case. Just adding, I think he may be talking about specific xsl:copy methods introduced in 2.0, but it was interesting he recomended using apply-templates instead of. Would using apply-templates in this case be a viable alternative to try or not. Apologies for showing my ignorance here, still haven't got my head round xsl yet. > > Gav... > > ----- Original Message ----- > From: "Ross Gardler" > To: > Sent: Friday, March 03, 2006 12:58 AM > Subject: Re: Forrestbot + SVN = mixed line-endings in HTML > > >> X-SpamKiller-AcctId: 1 >> X-SpamKiller-MsgId: 1129546381.12724 >> >> Web Maestro Clay wrote: >>> We have a new problem using forrestbot. Part of this could be my own >>> settings, but I am assured by Jeremias that this isn't completely the >>> case. Please see below. >>> >>>> On 02.03.2006 00:12:42 Clay Leeds wrote: >>>> >>>>> On Mar 1, 2006, at 1:28 PM, Jeremias Maerki wrote: >>>>> >>>>>> Wonderful. Just what I need. Different platforms, different line >>>>>> endings, no SVN properties set. And if I want to manually set them, >>>>>> SVN >>>>>> complains about mixed line endings in HTML files. Clay, would you >>>>>> mind >>>>>> asking the Forrest people how they deal with that or how we're >>>>>> supposed to deal >>>>>> with this? I'm not very amused to process each file separately >>>>>> until I have consistent line-endings and the right SVN properties >>>>>> and the >>>>>> next Forrest run might even take everything apart again. I liked the >>>>>> scp >>>>>> approach better. Sigh. >>>>> >>>>> >>>>> My bad... I don't have my SVN settings correct. I need to set my >>>>> svn:eol-style property to 'native' & then this shouldn't be a >>>>> problem. Sorry for the grief! >>>>> >>>>> I've made the change locally. I need to also do the same for my other >>>>> projects. >>>> >>>> >>>> Part of that may be due to your SVN settings, but I got mixed line >>>> endings in HTML files generated by Forrest. I haven't checked, yet, >>>> why >>>> this happens but that probably doesn't happen because of your SVN >>>> settings. >>>> >>>> Jeremias Maerki >>> >>> >>> Please advise. >> >> >> Can't be certain without more info about the specific problem. However, I >> strongly suspect this is a symptom of >> http://issues.apache.org/jira/browse/FOR-492 >> >> This, in turn, is caused by >> http://issues.apache.org/jira/browse/XALANJ-656 >> >> I'd like to say "its not our fault", but this Xalan is open source, just >> like Forrest, any one of us could fix the problem. Who will get the itch >> first? >> >> Ross >> >> Ross >