[
https://issues.apache.org/jira/browse/LUCENE-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-5283:
--------------------------------
Attachment: LUCENE-5283.patch
As a purely intellectual exercise I decided to investigate whether it's
possible to have a "top-level", after-all-the-submodules check for the number
of executed tests. Ant really isn't suited for multi-module, hierarchical
project layouts; it'd be so much easier with gradle...
Anyway, the attached patch seems to work. It's terribly hacky and terribly
ugly, but it does work. Try it from module-level or top-level (lucene or solr,
I didn't try to make it work at top-top level).
{code}
cd lucene
ant test -Dtests.class=*TestSpellChecker*
...
BUILD SUCCESSFUL
{code}
but:
{code}
ant test -Dtests.class=*foo*
...
BUILD FAILED
C:\Work\lucene-solr-svn\trunk\lucene\common-build.xml:1278: Not even a single
test was executed (a typo in the filter pattern maybe)?
{code}
Let me know what you think. Should I commit it? In spite of how ugly it is?
> 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, 5.0
>
> Attachments: 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.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
