[
https://issues.apache.org/jira/browse/DERBY-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500883
]
Daniel John Debrunner commented on DERBY-2743:
----------------------------------------------
Errors like this:
> ERROR 38000: The exception 'java.lang.NoClassDefFoundError:
> org.apache.derby.iapi.sql.dictionary.DataDictionaryContext' was thrown while
> evaluating an expression.
> ERROR XJ001: Java exception:
> 'org.apache.derby.iapi.sql.dictionary.DataDictionaryContext:
> java.lang.NoClassDefFoundError'.
are due to the tests using derby's internal apis. That class correctly was
removed in 10.3 for DERBY-2138.
It does show the danger of having tests use non-standard api's, at least if we
want to run tests from an old release against a new release.
I think that is a good goal and was one of the reasons I put effort behind
converting tests to JUnit, hopefully due to lack of master files it will be
easier to run 10.3 JUnit tests against future releases.
> Run 10.2 tests against 10.3 and evaluate to identify incompatibilities
> ----------------------------------------------------------------------
>
> Key: DERBY-2743
> URL: https://issues.apache.org/jira/browse/DERBY-2743
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derbyall_report.txt
>
>
> It would be good to do a run of 10.2 tests against 10.3 to see if there are
> any obvious incompatibilities
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
