I am Ahsan Shamsudeen from Computer Science & Engineering, University of Moratuwa. My proposal for Google summer of code is accepted. My project is "Improve Derby's code coverage". I need your kind support to complete this project in a successful manner.Below is the link to my project page
http://www.google-melange.com/gsoc/proposal/review/google/gsoc2013/speeduo/1 Thanks, Ahsan On Mon, Jun 3, 2013 at 8:25 PM, Knut Anders Hatlen (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-6213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673178#comment-13673178] > > Knut Anders Hatlen commented on DERBY-6213: > ------------------------------------------- > > Hi Rick, > > I agree that testing against the deprecated DataSources still has some > value. Note that I only changed the tests that had direct references to the > deprecated classes. Most of the tests obtain DataSources from the test > harness by calling JDBCDataSource.getDataSource(), which still returns > instances of the deprecated classes (using reflection, so there's no > warning). So most of the DataSource tests use the deprecated classes even > after these changes. > > > 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, deprecate-datasources.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, > derby-6213-20-aa-remove.java15.compile.classpath.diff, > derby-6213-21-aa-felixLint.diff, > derby-6213-22-aa-remove1.4and1.5sourceAndTargetLevels.diff, > derby-6213-23-aa-removeSimpleMobileApp.diff, > derby-6213-24-aa-makeBasicConnectionPoolDataSource40public.diff, > descriptor-lists.diff, releaseNote.html, releaseNote.html, > revive-sqlxmlutil-target.diff, simplify-with-java5.diff, > simplify-with-java5-v2.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 >
