Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Mon, 20 May 2013 13:55:15 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12646087.1367692196242.346693.1369058115736@arcas>
In-Reply-To: <JIRA.12646087.1367692196242@arcas>
References: <JIRA.12646087.1367692196242@arcas>
Subject: [jira] [Updated] (DERBY-6213) Deprecate support for Java 5 and CDC
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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-13-aa-lint4-implSqlConn.diff

Attaching derby-6213-13-aa-lint4-implSqlConn.diff. This patch generifies the code in the org.apache.derby.impl.sql.conn package. I am running tests now.

This ball of yarn pulled in the grammar. Generifying the grammar, in turn, required me to generify some code generated by javacc which is not in sqlgrammar.jj itself. Probably the right solution to this problem is to upgrade our version of javacc. However, I didn't want to keep pulling on the ball of yarn. Instead, I added some more expression rewriting to the build target which compiles the grammar. The build target now performs these transformations on the code invented by javacc:

     java.util.Vector ->  java.util.Vector<Object>
     java.util.Enumeration ->  java.util.Enumeration<Object>


Touches the following files:

M       java/engine/org/apache/derby/iapi/sql/conn/LanguageConnectionContext.java
M       java/engine/org/apache/derby/impl/sql/compile/TablePrivilegesNode.java
M       java/engine/org/apache/derby/impl/sql/compile/PrivilegeNode.java
M       java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
M       java/engine/org/apache/derby/impl/sql/compile/sqlgrammar.jj
M       java/engine/org/apache/derby/impl/sql/conn/GenericLanguageConnectionContext.java
M       java/engine/org/apache/derby/impl/sql/conn/GenericStatementContext.java
M       java/engine/org/apache/derby/impl/sql/build.xml
M       java/shared/build.xml

                
> 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: 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, 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