You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/06/09 19:46:03 UTC

[jira] [Resolved] (DERBY-4021) 'ant junit-lowmem' fails when classpath is not set

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

Kristian Waagan resolved DERBY-4021.
------------------------------------

    Resolution: Duplicate

Resolving as duplicate of DERBY-4089.

> 'ant junit-lowmem' fails when classpath is not set
> --------------------------------------------------
>
>                 Key: DERBY-4021
>                 URL: https://issues.apache.org/jira/browse/DERBY-4021
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.5.1.1
>         Environment: Apache Ant version 1.7.1 compiled on December 9 2008
>            Reporter: Kristian Waagan
>              Labels: derby_triage10_8
>
> 'ant junit-lowmem' fails with the following error when run with ant 1.7.1:
> <error message="org.apache.derbyTesting.functionTests.tests.memory._Suite" type="java.lang.ClassNotFoundException">java.lang.ClassNotFoundException: org.apache.derbyTesting.functionTests.tests.memory._Suite
>         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
>         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
>         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:169)
> Running the target with ant 1.6.5 on the same Derby revision works.
> It is not clear of the problem is due to ant only, or ant and changes in the build system . If the latter, it is most likely a classpath issue, as the class files are indeed built and included in the jar file.
> Other targets seems to be running fine.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira