SEARCH-732: Downgrade JFlex to 1.6.1 #60
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In JFlex 1.8.0, the type of `yychar` was changed from `int` to `long` [1]. This causes a compilation error when MusicbrainzTokenizerImpl.java is regenerated. We would otherwise need to copy the changes from [1] into our MusicbrainzTokenizerImpl.jflex file -- though regnerating it with 1.9.1 produces many other changes in the tokenizer which I don't know the implications of. At the very least we'd have to rebuild all indexes. JFlex was updated to 1.9.1 in 692c9ab (I assume only "for good measure"). [1] apache/lucene@af831d28
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In JFlex 1.8.0, the type of
yycharwas changed frominttolong[1]. This causes a compilation error when MusicbrainzTokenizerImpl.java is regenerated. We would otherwise need to copy the changes from [1] into our MusicbrainzTokenizerImpl.jflex file -- though regnerating it with 1.9.1 produces many other changes in the tokenizer which I don't know the implications of. At the very least we'd have to rebuild all indexes.JFlex was updated to 1.9.1 in 692c9ab (I assume only "for good measure").
[1] apache/lucene@af831d28