db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6213) Deprecate support for Java 5 and CDC
Date Tue, 07 May 2013 14:23:17 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-6213:

    Attachment: derby-6213-02-aa-org.apache.derby.vti.diff

Attaching derby-6213-02-aa-org.apache.derby.vti.diff. This patch converts the org.apache.derby.vti
package to Java 6. I am running tests now.

When I check this in, it's likely that we will begin to see failures in the test runs on Java
5 and CDC. This will be a sign that we need to stop running the trunk tests on those platforms.

Touches the following files:


M       java/engine/org/apache/derby/vti/build.xml

Simplified the build script.


M       java/engine/org/apache/derby/vti/ForeignTableVTI.java

Parameterized a HashMap usage.


D       java/engine/org/apache/derby/vti/VTITemplateBase.java
M       java/engine/org/apache/derby/vti/VTITemplate.java

Merged VTITemplateBase into VTITemplate. The first class was added as a trick to help people
write VTIs and table functions for Java 5 and CDC.

> 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:
>            Reporter: Rick Hillegas
>         Attachments: derby-6213-01-aa-collapsePublishedAPI.diff, derby-6213-02-aa-org.apache.derby.vti.diff
> The developer community has approved the proposal to sunset support for Java 5 and CDC:
> 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.

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