[
https://issues.apache.org/jira/browse/DERBY-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-4089:
-----------------------------------
Attachment: derby-4089-1b-set_classpath.diff
Attaching patch 1b (minor changes, i.e. comments).
> 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
> Assignee: Kristian Waagan
> Fix For: 10.9.0.0
>
> Attachments: derby-4089-1a-set_classpath.diff,
> derby-4089-1b-set_classpath.diff
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
