db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6126) compatibility._Suite fails if derbyTesting.jar lives in different directory than product jars
Date Sat, 27 Apr 2013 08:06:16 GMT

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

Kristian Waagan updated DERBY-6126:
-----------------------------------

    Attachment: derby-6126-1a-running_dist_jar_split_support.diff

Attaching patch 1a, which in addition to adding support for running off a distribution where
the test jar is stored in a different directory than the production jars, cleans up some comments
and renames a method getInstance to newInstance.

Note that neither having old distributions with "split jars" nor having distributions where
potentially all the jars are living in different directories are supported. It should however
be easier now to add this support if required.

Patch ready for review.
                
> 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
>         Attachments: derby-6126-1a-running_dist_jar_split_support.diff
>
>
> 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

Mime
View raw message