[
https://issues.apache.org/jira/browse/DERBY-5485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5485:
---------------------------------
Attachment: derby-5485-02-aa-fixBigDecimalInstantiators.diff
Attaching derby-5485-02-aa-fixBigDecimalInstantiators.diff. This fixes
org.apache.derbyTesting.functionTests.tests.jdbcapi.ProcedureTest so that it
runs on JDK 1.4 again. The previous patch broke that test because the compiler
was resolving BigDecimal instantiations to an initializer which was introduced
in Java 5. This patch changes those instantiations so that they are resolved to
an initializer which appears in JDK 1.4. For further information on this
problem, see the following derby-dev email thread:
http://old.nabble.com/need-theories-about-errors-seen-in-the-jdk-1.4-test-runs-td32842864.html#a32842864
I have successfully run the patched test on Java 6 and JDK 1.4. Committed at
subversion revision 1202276.
Touches the following file:
M
java/testing/org/apache/derbyTesting/functionTests/tests/jdbcapi/ProcedureTest.java
> Simplify PropertySetter so that it is less brittle and easier to maintain.
> --------------------------------------------------------------------------
>
> Key: DERBY-5485
> URL: https://issues.apache.org/jira/browse/DERBY-5485
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5485-01-af-simplifyPlusJavadoc.diff,
> derby-5485-01-ag-changeJDBClevel.diff, derby-5485-01-ah-changeJDBClevel.diff,
> derby-5485-02-aa-fixBigDecimalInstantiators.diff
>
>
> The PropertySetter task sets up classpath variables so that the build can
> take advantage of JVM-specific class libraries. Using those libraries makes
> it possible for the compiler to flag code which is supposed to run on less
> capable platforms but which calls methods from later JVMs. This is a very
> tricky problem and we seem to have reached consensus that it requires too
> much effort to make PropertySetter run correctly in all of the build
> environments which Derby developers use. I will attach a proposal for how to
> simplify PropertySetter so that it requires less effort to maintain.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
