Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1380084658.1236694730892.JavaMail.jira@brutus>
Date: Tue, 10 Mar 2009 07:18:50 -0700 (PDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4089) It should be possible to run unit
 tests right after "ant all"
In-Reply-To: <2121764174.1236694250840.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680470#action_12680470 ] 

Kristian Waagan commented on DERBY-4089:
----------------------------------------

I agree this problem should be addressed.
A few of the targets do set the classpath, most don't. 
It should be possible to easily override the classpath, as there are three sources; classes, sane jars and insane jars.

The classes directory is nice to use when doing development, as you don't have to wait for the jars to be built, but additional problems can be detected when running with the product jars.

> It should be possible to run unit tests right after "ant all"
> -------------------------------------------------------------
>
>                 Key: DERBY-4089
>                 URL: https://issues.apache.org/jira/browse/DERBY-4089
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 10.4.2.0
>            Reporter: Aaron Digulla
>
> Right now, the property "derby.junit.classpath" is empty by default. There should be an ant target which sets the correct classpath to run all tests after an initial checkout and "ant all".
> The current situation is very confusing to beginners and people who try to build Derby for the first time. For example, when running the tests, I got this exception:
> java.lang.ClassNotFoundException: org.apache.derbyTesting.junit.EnvTest
> but that class was there, the file was there, everything was correct. Googling for the error didn't turn anything up, either. It took me a while to believe that build.xml just wouldn't try to setup a classpath for the tests.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.