[
https://issues.apache.org/jira/browse/DERBY-4089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680514#action_12680514
]
Kristian Waagan commented on DERBY-4089:
----------------------------------------
Rick,
Do you consider both the sane and the insane jars as a production configuration?
I actually find that building the jars is a small burden when I do quick
iterative development. If we choose to use the jars as the default, I think we
should consider including the build target for the jars in the default target
(currently 'buildsource') or 'all'.
It's acceptable that the subsequent test run fails the first time when I
haven't built the jars, but after that first time my new code will be ignored
unless the jars are automatically updated. We could of course make the build
detect stale jars.
If we aim for testing of the production configuration, also for novice users /
casual developers, shouldn't we also include the 'clobber' target in the
default target?
Even experienced developers have checked in code that breaks the build or tests
because they didn't run the tests against jars, so I'm thinking there must be a
reason why [some] people choose the classes directory over the jars. I agree
that running with jars catches more issues, I feel the question is more whether
it should be the default configuration to do so or not ("out-of-the-box
experience"?).
> 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.
