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] Commented: (DERBY-4089) It should be possible to run unit tests right after "ant all"
Date Tue, 10 Mar 2009 15:00:53 GMT

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

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

Sounds like a good approach to me.
A problem with using the jars, is that novice users may end up running the tests against stale
code as the 'ant all' target doesn't rebuild the jar files.

> 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.


Mime
View raw message