[
https://issues.apache.org/jira/browse/LUCENE-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-3969:
----------------------------------
Attachment: LUCENE-3969.patch
New patch:
- I now have found out where the UOE comes from, it's the random parameter
generator. But this is nasty and should be solved better. I readded the catch
block with a comment.
In general, the code should be refactored to not call getConstrcutors all the
time. Instead the global list of List<Class<T>> should be replaced by
List<Constructor<T>>, then we only have one list where to choose the ctor from
(the class is implicit).
Will work on a patch.
> Use all (non-deprecated) analysis ctors in TestRandomChains
> -----------------------------------------------------------
>
> Key: LUCENE-3969
> URL: https://issues.apache.org/jira/browse/LUCENE-3969
> Project: Lucene - Java
> Issue Type: Bug
> Components: modules/analysis
> Reporter: Robert Muir
> Attachments: LUCENE-3969.patch, LUCENE-3969.patch, LUCENE-3969.patch,
> LUCENE-3969.patch
>
>
> We made TestRandomChains in LUCENE-3919, which reflects all
> analysis components from the classpath and builds analyzers from them,
> then checks consistency.
> but currently it only supports some tokenizers/tokenfilters/charfilters,
> because it hardcodes at certain ctors e.g. Tokenizer(Reader) and
> Tokenizer(Version+Reader).
> Instead we should use all ctors, just filling them in with random data of
> whatever argument type they take.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
