[
https://issues.apache.org/jira/browse/LUCENE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444809#comment-17444809
]
Dawid Weiss commented on LUCENE-9921:
-------------------------------------
Also, think this task is actually obsolete - I see this after an upgrade:
{code}
Script 'C:\Work\apache\lucene\gradle\generation\regenerate.gradle' line: 183
* What went wrong:
Execution failed for task ':lucene:analysis:icu:genUtr30DataFilesChecksumCheck'.
> Checksums mismatch for derived resources; you might have modified a generated
> resource (regenerate task: genUtr30DataFiles):
Current:
property:icu4j=70.1
Expected:
property:icu4j=68.2
{code}
So I think I might have fixed it at some point and forgot to close the issue?
> Can ICU regeneration tasks treat icu version as input?
> ------------------------------------------------------
>
> Key: LUCENE-9921
> URL: https://issues.apache.org/jira/browse/LUCENE-9921
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Robert Muir
> Priority: Major
>
> ICU 69 was released, so i was playing with the upgrade just to test it out
> and test out our regeneration.
> Running {{gradlew regenerate}} naively wasn't helpful, regeneration tasks
> were SKIPPED by the build.
> So I'm curious if the ICU version can be treated as an "input" to these
> tasks, such that if it changes, tasks know the generated output is stale?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
