[
https://issues.apache.org/jira/browse/DERBY-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680518#action_12680518
]
Aaron Digulla commented on DERBY-4089:
--------------------------------------
The default should work for most people, that's why it's the "default". As soon
as you know your way around the source, a developer can define his own property
file and override the default. But that simply doesn't work for novices.
Also, novices have no commit rights. So I can't see how making life harder for
them is going to help solve deeper development issues with Java and the Derby
team. :)
> 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.
