[
https://issues.apache.org/jira/browse/DERBY-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-3879:
-----------------------------
Attachment: DERBY-3879.zip
DERBY-3879.stat
DERBY-3879.diff
Attaching DERBY-3879.diff, DERBY-3879.stat, and DERBY-3879.zip, with the
following changes.
M src/getstart/twwdactivity1.dita
M src/getstart/twwdactivity1_Setup.dita
M src/getstart/twwdactivity3_Setup.dita
M src/getstart/twwdactivity2.dita
M src/getstart/twwdactivity4.dita
M src/tools/rtoolssysinfo1002629.dita
M src/devguide/cdevdvlp27715.dita
In twwdactivity1.dita (Creating a Derby database and running SQL statements),
the DERBYTUTOR directory was created within the Derby distribution. This is not
the best practice. Putting it in C:\DERBYTUTOR creates one fewer version number
to keep up with, so I've made that change.
In twwdactivity2.dita (Activity 2: Run SQL using the client driver), we
previously described the derby.log contents at the end of the activity as
follows:
Apache Derby Network Server - 10.2.2.0 - (485682) started and ready to
accept connections on port 1527 at 2007-05-04 20:04:33.511 GMT
... Database engine messages not shown ...
2007-05-04 20:08:43.883 GMT:
Shutting down instance c013800d-010f-82e9-fa03-00000011f280
This is not what appears in the log currently. The log appears to be erased
when I run ij, so at the end all that's there is the shutdown message. I'm
removing the paragraph about the log and the output from the topic, since the
log output is not helpful. (If anyone is concerned about this and wants
details, let me know.)
In twwdactivity3_Setup.dita (Activity 3: Run a JDBC program using the embedded
driver), I changed the dates and times to be more current and edited a line
that was too long.
In twwdactivity4.dita (Activity 4: Create and run a JDBC program using the
client driver and Network Server), I made the twwdactivity3_Setup.dita changes
as well as updating the startup and shutdown messages.
I also fixed some table formatting issues in this section of the Guide,
involving two more files (twwdactivity1_overview.dita and
twwdactivity1_Setup.dita).
In rtoolssysinfo1002629.dita (sysinfo example) I updated the version number and
also updated Java from 1.4.2 to 1.6, to set a good example for users.
In cdevdvlp27715.dita (Booting databases) I updated the derby.log output and
also changed "error log" to the more accurate "log file".
> Getting Started Guide has typo and version problems
> ---------------------------------------------------
>
> Key: DERBY-3879
> URL: https://issues.apache.org/jira/browse/DERBY-3879
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.2.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-3879.diff, DERBY-3879.stat, DERBY-3879.zip
>
>
> Mamta Satoor noticed the following in reviewing the 10.4.2 release:
> Just spotted 2 documentation issues (very trivial) in Getting Started
> with Derby. By no means, the release has to stop for them because i
> think these 2 minor issues have been with the docs for probably all
> the doc releases.
> 1)In the section 'Setting the environment variables", Step 1, for
> Windows says set DERBY_HOME=c:\Derby_10.
> We should not have the . at the end
> 2)In many different sections of this doc, we are showing incorrect
> version of ij and Derby (I think they are all showing 10.2. we should
> fix them to show 10.4 since we are talking about Derby 10.4 release).
> One example of such a place in this doc is the section "Creating a
> Derby database and running SQL statements" shows how to run ij in UNIX
> and Windows and then it shows the output from ij displaying the ij
> version. The output of ij for the 2 operating system in this section
> shows to be running ij10.2 rather than 10.4 as shown below. We need to
> fix the version number of ij in this section
> UNIX (Korn Shell) java -jar $DERBY_HOME/lib/derbyrun.jar ij
> ij version 10.2
> Windows java -jar %DERBY_HOME%\lib\derbyrun.jar ij
> ij version 10.2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
