[
https://issues.apache.org/jira/browse/DERBY-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6213:
--------------------------------------
Attachment: testcode.diff
Attaching testcode.diff which makes the test code compile against the Java 6
libraries. It adds quite a few new instances of unchecked warnings, and also
some deprecation warnings, that should be cleaned up later.
Almost all the test code was compiled against ${compile.classpath}, which is
supposed to point to the lowest supported platform. I changed compile.classpath
to point to java16compile.classpath rather than jsr169compile.classpath, as
Java 6 is now the lowest supported platform on trunk.
The compile.classpath property is not used much outside of the tests. However,
it is used in one build target for org.apache.derby.iapi.jdbc to ensure that
the classes work on JSR-169, and that target currently fails when it is
compiled against Java 6 libraries. I therefore changed the target to use
jsr169compile.classpath explicitly for now. I hope that doesn't interfere too
much with the changes Rick is doing in the same area.
Most changes are in build.xml files only. Some exceptions:
- Calls to ResultSet.updateBlob(int,Blob) and ResultSet.updateClob(int,Clob)
are ambiguous if the second argument is an untyped null, because JDBC 4
introduced ResultSet.updateBlob(int,InputStream) and
ResultSet.updateClob(int,Reader). Had to add some casts so that the compiler
would know which method to call.
- Test classes that implemented their own Blob, Clob or ResultSet classes
needed to add the new methods introduced in JDBC 4.
I've started the regression tests.
> Deprecate support for Java 5 and CDC
> ------------------------------------
>
> Key: DERBY-6213
> URL: https://issues.apache.org/jira/browse/DERBY-6213
> Project: Derby
> Issue Type: Improvement
> Components: Build tools, Documentation, Javadoc
> Affects Versions: 10.11.0.0
> Reporter: Rick Hillegas
> Attachments: derby-6213-01-aa-collapsePublishedAPI.diff,
> derby-6213-02-aa-org.apache.derby.vti.diff, derby-6213-03-aa-misc.diff,
> derby-6213-03-ab-misc.diff, derby-6213-04-aa-vtiPackageOnJava7.diff,
> derby-6213-05-ab-misc2.diff, derby-6213-06-aa-convertProductToJava6.diff,
> derby-6213-06-ab-removeCDC.diff,
> derby-6213-07-aa-restOfProductExceptJDBC.diff, revive-sqlxmlutil-target.diff,
> testcode.diff
>
>
> The developer community has approved the proposal to sunset support for Java
> 5 and CDC:
> http://apache-database.10148.n7.nabble.com/VOTE-Sunsetting-support-for-Java-5-and-CDC-td129832.html#a129925
> This issue tracks a number of tasks needed to implement this proposal:
> I) Remove build support for Java 5 and CDC.
> II) Purge user doc references to Java 5, CDC, and the JDBC 4 DataSources.
> III) Remove the JDBC 4 version of the public api from the published javadoc.
> The recently introduced CP2 DataSources would need to migrate to the JDBC 3
> version of the published javadoc. The JDBC 4 versions of the DataSources
> would still exist, but they would be vacuous extensions of their JDBC 3
> counterparts.
> IV) On the wiki, document our expectation that maintenance releases will
> support the same platforms as the original feature release cut from their
> branch.
> V) Decide what to do with the SimpleMobileApp. Probably we want to just
> remove this demo since its purpose is to show how to run Derby on the
> deprecated CDC platform.
--
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
