Hi Hartmut, On Mon, 5 Sep 2016 13:32:44 +0200 Hartmut Goebel <h.goe...@crazy-compilers.com> wrote:
> When specifying #:jar-file, the ant-builder will create a build.xml. > This build.xml did not include a test-target at all. So one *always* had > to include "#:tests? #f" to disable calling the (non-existing) > test-target - otherwise build would fail. But adding "#:tests? #f" is > just redundant. I see what you mean. But is it still possible to easily find out which packages have tests and which haven't after your patch? I think being able to know that is important since it's prudent to trust a package without tests (much) less. Also, would it be possible to auto-discover jUnit tests instead?
