Top posting:
I think you are correct, Laura, this section can be removed when
Working With Derby (WWD) and Getting Started are merged. In fact, I
don't think WWD will suffer if it were removed prior to the merge (but
that seems like it might be unnecessary work). The 'Introduction and
Prerequisites' section has become an unimportant artifact since the
derbyrun.jar was added to the system. Originally the exercises
described using the scripts in the framework subdirectories, these
relied on JAVA_HOME being set and insuring this was the main purpose of
the initial section. After derbyrun.jar was created a quick rewrite was
done but the need for the initial chapter was not revisited.
It might be good if information on setting up and verifying the JAVA
installation were added to the 'Setting up your environment' section of
the Getting Started Guide but I don't see it covered anywhere in the
manual currently. Because of all the platform related issues related to
setting up the software I opted not to cover this in Working With Derby
(WWD).
Laura Stewart wrote:
Kim - Appreciate the explanation. I was thinking that this might get
covered in DERBY-2390.
On 3/1/07, Kim Haase <[EMAIL PROTECTED]> wrote:
Well, setting the JAVA_HOME variable and setting your PATH to include
JAVA_HOME/bin are two separate steps. The instructions tell you to set
JAVA_HOME but not to set your PATH, so the table shows how to run the
command if you haven't set your PATH.
I think you've identified a problem with the instructions -- they ought
to tell you to set your PATH, because the subsequent instructions on
using the javac and java commands assume you've set it. We need a new
step 2 that tells you to set the PATH; then people can just run "java
-version" without specifying JAVA_HOME/bin. Should be a quick fix if you
can file a JIRA issue.
Thanks for noticing this.
Kim
Laura Stewart wrote:
> Hi -
>
> In the Working with Derby guide, there is a section (Introduction and
> Prerequisites) that has us check our version of java by running the
> java -version command. Then there is a table showing a path. I can
> run the java -version command from any path to get the info... so I
> find the path in the table confusing.
> I feel like I am missing something... What is it telling me?
>