[
https://issues.apache.org/jira/browse/LUCENE-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794635#action_12794635
]
Uwe Schindler commented on LUCENE-2122:
---------------------------------------
Some additional infos about the Hudson failure:
In the past Hudson used an internal junit.jar to do the testing, which was in
version 4 (the exact version can only be found out by one with hudson access,
Mike?). So Hudson was always using Junit4 for testing even in Lucene 2.9. After
the clover updates, we removed this JUnit lib path from the ANT command line
and therefore also hudson uses 4.7 as shipped with the svn checkout.
If it is really a JUnit problem, it seems to only occur with version 4.7. But I
am not sure, I still stink it may be a thread starvation problem (slow test) or
some local time problem that occurred two nights ago.
> Use JUnit4 capabilites for more thorough Locale testing for classes deriving
> from LocalizedTestCase
> ---------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2122
> URL: https://issues.apache.org/jira/browse/LUCENE-2122
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Other
> Affects Versions: 3.1
> Reporter: Erick Erickson
> Priority: Minor
> Fix For: 3.1
>
> Attachments: LUCENE-2122-r2.patch, LUCENE-2122-r3.patch,
> LUCENE-2122-r4.patch, LUCENE-2122.patch, LUCENE-2122.patch
>
>
> Use the @Parameterized capabilities of Junit4 to allow more extensive testing
> of Locales.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
