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 Thu, 23 May 2013 20:03:21 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-18-aa-collapseEmbeddedDataSources.diff

Attaching derby-6213-18-aa-collapseEmbeddedDataSources.diff. This patch collapses the *40
embedded data sources into their non *40 superclasses. I need to adjust the javadoc further.
I am running tests now.

With this patch, the *40 data sources become vacuous extensions of their non *40 superclasses.
I also note the following curiosity:

o Now BasicEmbeddedDataSource40 is a vacuous extension of EmbeddedBaseDataSource.

This makes me wonder whether we could rework the DataSource graph further and eliminate all
of the Basic* DataSources from the public javadoc, leaving us with just the *Base* versions.
That might help clarify to users how we name our DataSources. But that is outside the scope
of this patch.

Touches the following files:

M       java/engine/org/apache/derby/jdbc/EmbeddedDataSource.java
M       java/engine/org/apache/derby/jdbc/BasicEmbeddedDataSource40.java
M       java/engine/org/apache/derby/jdbc/EmbeddedConnectionPoolDataSource40.java
M       java/engine/org/apache/derby/jdbc/EmbeddedXADataSource40.java
M       java/engine/org/apache/derby/jdbc/EmbeddedDataSource40.java
M       java/engine/org/apache/derby/jdbc/EmbeddedConnectionPoolDataSource.java
M       java/engine/org/apache/derby/jdbc/EmbeddedXADataSource.java

> 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: buildbreak2-datasource.diff, buildbreak.diff, client.diff, 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, derby-6213-08-ab-jdbc.diff,
derby-6213-09-ab-lint1.diff, derby-6213-10-aa-lint2-implServices.diff, derby-6213-11-aa-lint3-implStore.diff,
derby-6213-12-aa-lint4-implSqlCatalog-implSqlDepend.diff, derby-6213-13-aa-lint4-implSqlConn.diff,
derby-6213-14-aa-lint6-implSqlCompile-implSqlExecute.diff, derby-6213-15-aa-lint7.diff, derby-6213-16-aa-lint8.diff,
derby-6213-17-aa-lint9.diff, derby-6213-17-ab-lint9.diff, derby-6213-18-aa-collapseEmbeddedDataSources.diff,
descriptor-lists.diff, revive-sqlxmlutil-target.diff, testcode.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.
> 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

View raw message