[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565325#comment-14565325
]
Dawid Weiss commented on LUCENE-5283:
-------------------------------------
Hi Steve. This must be a regression again. The problem here is that it's very
difficult to tell whether a module build is stand-alone or has been invoked by
(some) parent ant process. In effect it's very difficult to tell whether there
really was no tests or maybe it's just that tests have been filtered out for
this particular module.
I'm tired of this because it's such a pain to maintain and at the same time
there are no good solutions -- either somebody will be complaining that all
tests can be filtered out and not cause a failure or experience what you have
experienced.
I'll see if there's a way to add this "tests.ifNoTests" property, but I don't
see much sense to it -- either the check for the total number of tests works or
it doesn't. Why skip something that doesn't work anyway.
> Fail the build if ant test didn't execute any tests (everything filtered out).
> ------------------------------------------------------------------------------
>
> Key: LUCENE-5283
> URL: https://issues.apache.org/jira/browse/LUCENE-5283
> Project: Lucene - Core
> Issue Type: Wish
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 4.6, Trunk
>
> Attachments: LUCENE-5283-permgen.patch, LUCENE-5283.patch,
> LUCENE-5283.patch, LUCENE-5283.patch
>
>
> This should be an optional setting that defaults to 'false' (the build
> proceeds).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]