[
https://issues.apache.org/jira/browse/DERBY-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624117#comment-13624117
]
Myrna van Lunteren commented on DERBY-6126:
-------------------------------------------
This location/format for the compatibility test is new with 10.10. The tests
were rewritten to conform to our current junit mechanism - see DERBY-2067.
So I think we could see this as a regression.
Note also that previous mishaps with the split location of
derbyTesting.jar/other jars in the distribution have happened before, e.g.
DERBY-3602, DERBY-4806; and it's related to enhancements in the build so the
jars are always separate and we'd catch these before release time (assuming
we'd start testing with the classpath set up that way), see DERBY-1593 and
DERBY-1792.
> compatibility._Suite fails if derbyTesting.jar lives in different directory
> than product jars
> ---------------------------------------------------------------------------------------------
>
> Key: DERBY-6126
> URL: https://issues.apache.org/jira/browse/DERBY-6126
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.1.1
> Reporter: Knut Anders Hatlen
>
> Seen when testing the 10.10.1.1 release candidate. In the releases,
> derbyTesting.jar lives in the test sub-directory and the product jars live in
> the lib directory. This breaks an assumption in the compatibility test
> framework, and suites.All won't even start. It works fine if you move
> derbyTesting.jar into the same directory as the product jars.
> FAILED to invoke
> org.apache.derbyTesting.functionTests.tests.compatibility._Suite
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.apache.derbyTesting.functionTests.suites.AllPackages.invokeSuite(AllPackages.java:179)
> at
> org.apache.derbyTesting.functionTests.suites.AllPackages.addSuiteByReflection(AllPackages.java:149)
> at
> org.apache.derbyTesting.functionTests.suites.AllPackages.suite(AllPackages.java:61)
> at org.apache.derbyTesting.functionTests.suites.All.suite(All.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.runner.BaseTestRunner.getTest(BaseTestRunner.java:126)
> at junit.textui.TestRunner.start(TestRunner.java:184)
> at junit.textui.TestRunner.main(TestRunner.java:143)
> Caused by: java.lang.IllegalStateException: failed to get running
> distribution (programming error?)
> at
> org.apache.derbyTesting.functionTests.tests.compatibility.VersionCombinationConfigurator.getRunningDistribution(VersionCombinationConfigurator.java:299)
> at
> org.apache.derbyTesting.functionTests.tests.compatibility.VersionCombinationConfigurator.filterVersions(VersionCombinationConfigurator.java:266)
> at
> org.apache.derbyTesting.functionTests.tests.compatibility.VersionCombinationConfigurator.addTests(VersionCombinationConfigurator.java:169)
> at
> org.apache.derbyTesting.functionTests.tests.compatibility._Suite.addVersionCombinations(_Suite.java:81)
> at
> org.apache.derbyTesting.functionTests.tests.compatibility._Suite.suite(_Suite.java:135)
> ... 15 more
--
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
