[
https://issues.apache.org/jira/browse/LUCENE-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12497276
]
Paul Elschot commented on LUCENE-885:
-------------------------------------
> Paul: i can't reproduce the problem you describe..
That's good news, especially with you having more tests pass.
I may have to restart from a fresh checkout instead of using my working copy.
As for the preferred way of running single contrib tests, a better way to
phrase my question would probably be: What facilities of the lucene build.xml
can be used (imported) in the build.xml of a single contrib?
I remember creating the build.xml file for surround by starting from the lucene
build.xml.
That means there is probably some redundancy left in the current build.xml of
surround with respect to the lucene build.xml, and I'd like to remove that
redundancy.
> 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
> Assigned To: Hoss Man
> Attachments: 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]
