Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 25706 invoked from network); 14 Aug 2005 02:37:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Aug 2005 02:37:58 -0000 Received: (qmail 55053 invoked by uid 500); 14 Aug 2005 02:37:57 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 55011 invoked by uid 500); 14 Aug 2005 02:37:57 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 54998 invoked by uid 99); 14 Aug 2005 02:37:56 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2005 19:37:56 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of jta@bristowhill.com designates 66.75.162.133 as permitted sender) Received: from [66.75.162.133] (HELO ms-smtp-01-eri0.socal.rr.com) (66.75.162.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Aug 2005 19:38:17 -0700 Received: from [192.168.15.53] (cpe-204-210-23-212.san.res.rr.com [204.210.23.212]) by ms-smtp-01-eri0.socal.rr.com (8.12.10/8.12.7) with ESMTP id j7E2bqFf017290 for ; Sat, 13 Aug 2005 19:37:52 -0700 (PDT) Message-ID: <42FEAE7F.7000709@bristowhill.com> Date: Sat, 13 Aug 2005 19:37:51 -0700 From: "Jean T. Anderson" User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derby Development Subject: [WEB] fyi on dueling operating system forrest builds Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Under forrest 0.6, we had an issue with forrest on Windows generating odd diffs for three files under build/site/skin (print.css, screen.css, and basic.css). I mentioned it to the forrest-dev list as an FYI (I included a copy of that post down below). Andrew checked in those modified files on Windows and I found I didn't have any problems building on Linux. Andrew committed the forrest 0.7 upgrade under Windows, and after a forrest 0.7 build on Linux, I'm now seeing these diffs: [jta@gertie3 trunk]$ cd build/site/skin [jta@gertie3 skin]$ svn status M profile.css.xslt M profile.css M forrest.css.xslt M images/txtdoc.svg.xslt M screen.css M basic.css I did an 'svn revert' on these files before committing changes because I want to pursue this a little more. Everything displays fine for me locally, but I'll watch for any issues after the changes sync to www.apache.org. Just be aware that there could be some display issues -- and I apologize for any inconvenience in advance. These are one of those things that just don't become apparent until we sync the changes to www.apache.org. -jean -------- Original Message -------- Subject: Platform-specific svn diffs for three build/site/skin/*.css files Date: Tue, 02 Aug 2005 16:55:45 -0700 From: Jean T. Anderson Reply-To: dev@forrest.apache.org To: dev@forrest.apache.org This is minor, so unless you're curious and have bandwidth, don't worry. I had an opportunity to mention this to David Crossley at ApacheCon and he suggested pinging the list. This occurs on forrest 0.6. I originally committed Derby web site (http://db.apache.org/derby) files on a linux machine. The repo is at https://svn.apache.org/repos/asf/db/derby/site/trunk . If you build the site on a Windows machine, svn says there are diffs for 3 out of the 5 generated build\site\skin\*.css files: C:\jta\...\trunk>svn status build\site\skin M build\site\skin\print.css M build\site\skin\screen.css M build\site\skin\basic.css All of the style sheets have svn:eol-style set to native: C:\jta\...\trunk\build\site\skin>svn propget svn:eol-style *.css basic.css - native page.css - native print.css - native profile.css - native screen.css - native The main thing I notice is print.css, screen.css, and basic.css don't have a newline at the end of the file, while page.css and profile.css do. And it doesn't cause a problem -- just confusion as other Derby developers build the web site and try to understand what changed. Does this ring a bell to anyone? thanks, -jean p.s. the derby release monster will commit web site changes on windows probably tomorrow, after which I expect linux to show diffs p.p.s. next on my list is to upgrade to derby site to 0.7 ....