db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2224) Test harness should support J2ME 1.1
Date Fri, 19 Jan 2007 01:38:30 GMT

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

Myrna van Lunteren resolved DERBY-2224.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.3.0.0
       Derby Info:   (was: [Patch Available])

committed change 497678, see: http://svn.apache.org/viewvc?view=rev&revision=497678 
commit comment: 
DERBY-2224 - update j9_foundation master/canons to weme 6.1 (J2ME 1.1) results
- this change includes a change to ij because java.math.BigDecimal
  is now available, but JSR169 does not support methods like
  ResultSet.getBigDecimal(...).
- this change also accepts incorrect behavior in timestampArith.java, which is
  covered in DERBY-2225.


> Test harness should support J2ME 1.1
> ------------------------------------
>
>                 Key: DERBY-2224
>                 URL: https://issues.apache.org/jira/browse/DERBY-2224
>             Project: Derby
>          Issue Type: Test
>          Components: Test
>    Affects Versions: 10.2.2.0, 10.3.0.0
>            Reporter: Myrna van Lunteren
>         Assigned To: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-2224_tests_20070116.diff, DERBY-2224_tests_20070116.stat,
DERBY-2224_tests_20070118.diff, DERBY_2224_harness.diff, DERBY_2224_tests.diff
>
>
> I would like to enable the 'old' test harness to support the new version of IBM's j2ME
implementation, which is based on j2ME jdk spec version 1.1. This is available with a product
named Websphere Everyplace Micro Edition 6.1. from IBM.
> We already support j9_foundation, which matches to j2ME jdk spec 1.0. I'd like to add
j9_foundation11, which then matches to j2ME jdk spec 1.1.
> I'm proposing to switch my automated tests over to the newer version going forward, and
to minimize complexity of the change, I'd like to make the canons reflect behavior of the
new version. The differences are minimal. However, I want to be able to still run with the
old (except where the results differ, failures would occur with the old version).
> One of the reasons for moving to the new version is that there is a bug with the older
version in regards to security manager, preventing a smooth run of the junit tests, and I'd
like to run all short-running tests (suites.All and derbyall) with at least one of the versions.
Another reason is that the j2ME spec 1.0 is really old.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message