[
https://issues.apache.org/jira/browse/DERBY-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan resolved DERBY-2076.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.10.0.0
Issue & fix info: (was: Patch Available)
Resolving issue.
There is one potential issue, reported by Mamta on derby-dev [1]. If we want to
change the current intended behavior, that can be done under a separate issue.
[1]
http://mail-archives.apache.org/mod_mbox/db-derby-dev/201210.mbox/%3CCAFy7pk81zco6C5wQU2Ud2GhLP=zpuxtp37op-o+0eabejtw...@mail.gmail.com%3E
> Rewrite junitTests/derbyNet/CompatibilityTest to conform to current JUnit
> usage
> -------------------------------------------------------------------------------
>
> Key: DERBY-2076
> URL: https://issues.apache.org/jira/browse/DERBY-2076
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.3.1.4
> Reporter: Andrew McIntyre
> Assignee: Kristian Waagan
> Priority: Minor
> Fix For: 10.10.0.0
>
> Attachments: compiler-level.patch,
> derby-2076-0a-modernized_compat_test_preview.diff,
> derby-2076-0b-modernized_compat_test_preview.diff,
> derby-2076-1a-initial.diff, derby-2076-1b-initial.diff,
> derby-2076-2a-enable_test.diff
>
>
> The test
> org.apache.derbyTesting.functionTests.tests.junitTests.DerbyNet.CompatibilityTest
> has been failing in the nightlies because it needs to be run in the old test
> harness, and for some reason the property which grants permission to read
> ${user.home}/junit.properties is not being picked up properly in the old
> harness.
> I am able to resolve the problem by granting permission to read
> ${user.home}/junit.properties to all, but the test should be refactored so
> that it can run with the rest of the junit tests without needing the old
> harness.
--
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
