Hi, Kristian. I checked in the simple change, revision 231524. I'm
assuming JIRA items are really not required even for little fixes to
BUILDING.txt like this...
Thanks,
David
Kristian Waagan wrote:
Hello,
Today I was setting up the environment to be able to build Derby on a
new machine. I quickly browsed through the BUILDING.txt file, and by
mistake I set both 'j13lib' and 'j14lib' to 'JDK1?_HOME/lib' instead of
'JDK1?_HOME/jre/lib'. After a short moment of temporary confusion, I
realized why I did the mistake. In the section that describes what kind
of slashes to use in path names on Windows, the example value for
'j13lib' is 'c:/jdk1.3.1_15/lib'. This section comes in front of the
sections that actually describe what the values should be.
Although this is a tiny, tiny "improvement", I suggest setting the
example value to 'c:/jdk1.3.1_15/jre/lib' to avoid unnecessary errors
caused by not reading the documentation carefully ;) The updated section
is included below for completeness.
If I need to take further actions to get this change done (JIRA -> patch
-> review -> commit), let me know!
--
Kristian
>>> From BUILDING.txt, changed lines marked with '>':
NOTE TO WINDOWS USERS: *use forward slashes* ("/") in your
path specifications. Backward-slashes ("\") confuse Ant.
Check your path specifications for correct use of slashes in
ant.properties if you get errors during the build saying java.lang
can not be found.
For example, you should have:
> j13lib=c:/jdk1.3.1_15/jre/lib
NOT
> j13lib=c:\jdk1.3.1_15\jre\lib
begin:vcard
fn:David Van Couvering
n:Van Couvering;David
org:Sun Microsystems, Inc.;Database Technology Group
email;internet:[EMAIL PROTECTED]
title:Senior Staff Software Engineer
tel;work:510-550-6819
tel;cell:510-684-7281
x-mozilla-html:TRUE
version:2.1
end:vcard
