[
https://issues.apache.org/jira/browse/DERBY-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrna van Lunteren closed DERBY-1977.
-------------------------------------
Resolution: Won't Fix
Marking this Won't fix.
I think most people now either use either (still) the textui Runner, or the
junit targets, or other mechanisms (such as Jenkins), rather than the gui
runners.
> Let GUI TestRunners run JUnit tests without the -noloading option
> -----------------------------------------------------------------
>
> Key: DERBY-1977
> URL: https://issues.apache.org/jira/browse/DERBY-1977
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.2.1.6
> Reporter: Dyre Tjeldvoll
>
> Kristain Waagan wrote in a message on derby-dev:
> > The problem is that the GUI runners are using a custom classload to
> > allow for dynamic reloading of the test classes. It defeats the getURL
> > method in SecurityManagerSetup, seemingly by returning an empty/null
> > (the object itself isn't null) ProtectionDomain object. This finally
> > leads to the URL object extracted being null, which causes the NPE.
> >
> > A workaround is to specify the -noloading option for the runner, like this:
> > java -classpath X junit.swingui.TestRunner -noloading
> > org.apache.derbyTesting...
> >
> > If you do this, you must restart the GUI if you recompile the test classes.
> > We should investigate this and see if we can get it working without
> > specifying the -noloading argument.
--
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
