db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5938) Documentation says Derby works with Java 1.4.2
Date Wed, 10 Oct 2012 21:33:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13473581#comment-13473581

Kim Haase commented on DERBY-5938:

There's a small problem with the "SYSXPLAIN_STATEMENTS system table" topic, http://db.apache.org/derby/docs/dev/ref/rrefsysxplain_statements.html.
The JVM_ID column is described as follows:

A code indicating what version of the JVM was running when this statement was captured: '4'
for J2SE_14 (JDK 1.4.0 or 1.4.1), '5' for J2SE_142 (JDK 1.4.2), '6' for J2SE_15 (JDK 1.5),
or '7' for J2SE_16 (JDK 1.6).

I have no problem with removing the items for JDK 1.4, since it is no longer supported --
though it makes the numbering scheme seem odd. But there should also be an entry for JDK 7,
and eventually JDK 8, etc. It appears that the code for JDK 7 is '8', as would be expected
(I tried). It seems as if this topic might need to be updated every time we support a new
JDK release if left as is.

Also, the names should not be "J2SE" nor should they be "1.x" -- they are Java SE 5, Java
SE 6, etc. Since these supposed constants don't seem to be hard-coded anywhere, I'm thinking
of changing the topic to say:

A code indicating what version of the JVM was running when this statement was captured. The
code is a character that represents the release number plus one. For example, the code for
Java SE 6 is '7', and the code for Java SE 7 is '8'. 

That way, we might not have to update it for every single release.

> Documentation says Derby works with Java 1.4.2
> ----------------------------------------------
>                 Key: DERBY-5938
>                 URL: https://issues.apache.org/jira/browse/DERBY-5938
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
> The documentation says that Derby works with Java 1.4.2. This is not true on trunk, as
support for Java 1.4.2 is removed for Derby 10.10. A quick search came up with these places
that need change:
> * Getting started guide:
> http://db.apache.org/derby/docs/dev/getstart/tgssetupverify.html
> http://db.apache.org/derby/docs/dev/getstart/cgstutorialintro.html
> http://db.apache.org/derby/docs/dev/getstart/tgssetupjavaenvir.html
> http://db.apache.org/derby/docs/dev/getstart/cgsintsr.html
> Need to change the above topics to say that you need JDK 1.5 or later installed to run
the examples.
> * Developer's guide:
> http://db.apache.org/derby/docs/dev/devguide/rdevconcepts713.html
> The cell for the combination Multi-User/Embedded mentions potential multi-boot problems
in pre-1.4 JVMs. Derby doesn't run on pre-1.4 JVMs anymore (and hasn't done for a long time).
However, the multi-boot problem is present on CDC/FP 1.1, which is still a supported platform,
so maybe we should change "pre-1.4" to "J2ME" (or however we usually refer to that platform
in the docs).
> * Admin guide:
> http://db.apache.org/derby/docs/dev/adminguide/cadminappsthenetworkserverandjvms.html
> Should say that the server is compatible with Java 5 and above.
> * Tools guide:
> http://db.apache.org/derby/docs/dev/tools/ctools1003034.html
> Although it's technically correct that the tools do run on Java 1.4, it's not possible
to access a Derby database with them on Java 1.4 in any supported way (unsupported way: use
derbytools.jar from 10.10 and derby.jar from 10.9). So we should change this topic to say
Java 5 and above, perhaps also mentioning CDC/Foundation Profile 1.1.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message