Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Fri, 05 Sep 2008 19:17:59 +0200
From: Knut Anders Hatlen <Knut.Hatlen@Sun.COM>
Subject: Re: building the Derby website
In-reply-to: <48C13CAE.4080802@sun.com>
Sender: Knut.Hatlen@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x6y726h5q0.fsf@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <48C13CAE.4080802@sun.com>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (usg-unix-v)

Rick Hillegas <Richard.Hillegas@Sun.COM> writes:

> I am getting ready to refresh the Derby website. I don't do this often
> and my impression is that over the course of a year, the process
> morphs a little. I wanted to get a sanity check of what I'm seeing
> today. I just refreshed my website client with an "svn update" command
> and then I built the website using the "forrest site" command.
>
> According to item (6) of the website-building instructions
> (http://db.apache.org/derby/papers/derby_web.html), after this build I
> should expect that my "svn status" command will show that the build
> has touched files under build/site/skin and build/site/papers. I am
> seeing that. In addition, I am seeing that the build has touched files
> under
>
>  build/site
>  build/site/integrate
>  build/site/manuals
>  build/site/release

Hi Rick,

I see this too. All the files are generated png files, and I believe it
is safe to revert all of them. At least, that's what I did when I
updated the website a couple of days ago.

-- 
Knut Anders