db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1105) derbyall failures due to change in exception type
Date Thu, 16 Mar 2006 14:54:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1105?page=comments#action_12370693 ] 

Myrna van Lunteren commented on DERBY-1105:

(adding my comment from the list into this bug)

I looked at some of the diffs, and I think for at least a number of jdk16 canons, a better
alternative would be to add some sed-ing to the test harness' Sed.java class, and replace
the string with something common, and update the 'original' master and canons for other jvms.

It may seem like more work now, but I know from experience that maintaining canons is an uninteresting,
bothersome task...
To begin with, add a replacement line in Sed.java so that both 'java.sql.SQLException' and
'SQL Exception' get replaced by something common, for instance, 'xxSQL-Exception:xx '
That should get rid of at least some of the canons. I am not sure how important it is to retain
for instance the java.sql.SQLTransientConnectionException in checkDataSource.out, but I think
the above should be pretty acceptable and a good first step to minimize the number of jdk16

> derbyall failures due to change in exception type
> -------------------------------------------------
>          Key: DERBY-1105
>          URL: http://issues.apache.org/jira/browse/DERBY-1105
>      Project: Derby
>         Type: Sub-task
>     Versions:
>  Environment: jdk 1.6
>     Reporter: Anurag Shekhar
>     Assignee: Anurag Shekhar
>  Attachments: derby-1105.diff.gz, derby-1105.stat
> due to change in exception type in embedded driver there are several failures in derbyall
under jdk1.6. The out file ot the test case should be changed in such a way that it works
on jdk1.6 and older jdk's without fails

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message