[
https://issues.apache.org/jira/browse/LUCENE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12502576
]
Steven Parkes commented on LUCENE-885:
--------------------------------------
Whoops, the primary failure was because I wasn't up to date.
Actually, making test-contrib rely on build-contrib doesn't fix it either. It's
"test-compile-contrib" (if you will) that fails and rather being
contrib-crawled, that's only done as the target of "test" in each contrib
directory, at which point, it's running in the protected contrib-crawl.
Easy enough to lift this loop into another target, e.g., build-contrib-test.
And that will start surfacing errors, which I can work through.
I've got patches. Want them on this JIRA or another?
> clean up build files so contrib tests are run more easily
> ---------------------------------------------------------
>
> Key: LUCENE-885
> URL: https://issues.apache.org/jira/browse/LUCENE-885
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Build
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 2.2
>
> Attachments: LUCENE-885.patch, LUCENE-885.patch
>
>
> Per mailing list discussion...
> http://www.nabble.com/Tests%2C-Contribs%2C-and-Releases-tf3768924.html#a10655448
> Tests for contribs should be run when "ant test" is used, existing "test"
> target renamed to "test-core"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
