[
https://issues.apache.org/jira/browse/LUCENE-6993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15154936#comment-15154936
]
Mike Drob commented on LUCENE-6993:
-----------------------------------
Question about what is proper behaviour in terms of backwards compatibility
here...
Upgrading JFlex from 1.6.0 to 1.6.1 (and 1.7.0, I assume) changes the generated
output. I have no idea if the behaviour is identical between the new class
files and the old. I imagine that we want to keep the Impls generated by the
old version when operating with an old lucene match version, rather than
regenerating those with the new jflex. If so, I'll drop the work I did on
updating jflex-legacy task, since it doesn't make sense to keep around (it
woudn't generate code to match what is in source control).
Does this make sense?
> Update UAX29URLEmailTokenizer TLDs to latest list, and upgrade all
> JFlex-based tokenizers to support Unicode 8.0
> ----------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-6993
> URL: https://issues.apache.org/jira/browse/LUCENE-6993
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis
> Reporter: Mike Drob
> Assignee: Robert Muir
> Fix For: 6.0
>
> Attachments: LUCENE-6993.patch, LUCENE-6993.patch, LUCENE-6993.patch,
> LUCENE-6993.patch, LUCENE-6993.patch
>
>
> We did this once before in LUCENE-5357, but it might be time to update the
> list of TLDs again. Comparing our old list with a new list indicates 800+ new
> domains, so it would be nice to include them.
> Also the JFlex tokenizer grammars should be upgraded to support Unicode 8.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
