On 6/30/06, Boris Unckel <[EMAIL PROTECTED]> wrote:
Hello,
there were some questions for different components in the style "is xyz
compatible with JDK 1.x" in the last weeks.
I know that commons-logging did several tests and put some mentionable
work on JDK 1.2 compatibility.
This information seems important to me, there should be one distinct
place, where people can look that up.
A table with:
Component | Sun JDK 1.2 | Sun JDK 1.3.1_xx | Sun JDK 1.4.0_xx | Sun JDK
1.4.1_xx | Sun JDK 1.4.2_xx | IBM JDK 1.4.2 Build xx | Sun JDK 1.5.0_xx
| Official Build was done with
should show what currently is tested. For each JDK release the test
should be done with the highest available JDK patch level, which should
be documented in the table.
To achieve this information each component should be build with the
corresponding JDK (source and target set to the corresponding Java version)
and all JUnit tests must be clean.
I think many components already test that, but there is no central
documentation, and the tests are not mandatory.
Especially for older JDK versions this information is important, maybe
JDK 1.5 causes problems.
What do you think?
@Release-/Buildmanagers: Which JDKs/versions did you test for which
component?
Components which are built with maven add a non-standard element to
the manifest indicating the values of the "compile.source" and
"compile.target" properties when it was built. So for example these
are both set to 1.3 for Commons Chain and in the Chain 1.1 jar's
manifest you see:
X-Compile-Source-JDK: 1.3
X-Compile-Target-JDK: 1.3
Along with the build JDK, which in this case was JDK 1.4.2_12
http://jakarta.apache.org/commons/chain/downloads.html
You also usually get the junit test report which was generated when
the release was built:
http://jakarta.apache.org/commons/chain/junit-report.html
This isn't anywhere near what you're asking and we should have at
least the "minimum JDK" indicated - but the release managers job is
hard enough that I wouldn't want to require testing on all those JDK's
- I think we're probably doing well if we manage three of them (I did
JDK 1.3.1_04, 1.4.2_12 and 1.5.0_06 for Chain 1.1).
We could add a paragraph to the "preparing a release" page with a
reminder to test on as many JDK versions as possible:
http://jakarta.apache.org/commons/releases/prepare.html
Niall
Regards
Boris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
