db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6243) Fold Java5ClassFactory into ReflectClassesJava2
Date Mon, 03 Jun 2013 12:21:20 GMT

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

Knut Anders Hatlen updated DERBY-6243:
--------------------------------------

    Attachment: derby-6243-01-a.diff

The attached patch moves functionality from Java5ClassInspector to ClassInspector, and removes
Java5ClassInspector and Java5ClassFactory.

Other related changes:

- modules.properties: Remove entry for Java5ClassFactory so that ReflectClassesJava2 is used
on all platforms.

- SQLState.java: Remove VM_LEVEL_TOO_LOW which is no longer used now that the Java 5 functionality
is available in all versions of the ClassFactory.

- messages.xml: Remove message for the removed SQLState.

- UngroupedAggregatesNegativeTest.java: Remove test case for the removed SQLState. The test
case was already disabled on Java 5 and higher, but the patch also removed the code.

All the regression tests ran cleanly with the patch.
                
> Fold Java5ClassFactory into ReflectClassesJava2
> -----------------------------------------------
>
>                 Key: DERBY-6243
>                 URL: https://issues.apache.org/jira/browse/DERBY-6243
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: derby-6243-01-a.diff
>
>
> There are two ClassFactory implementations: ReflectClassesJava2 for Java 1.4 and lower
(including CDC/FP 1.1) and Java5ClassFactory for Java 5 and higher. Now that the base level
on trunk is Java 6, it is sufficient with one ClassFactory.

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

Mime
View raw message