[jira] [Commented] (LUCENE-9921) Can ICU regeneration tasks treat icu version as input?

["Arjen (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443572#comment-17443572 ] 

Arjen commented on LUCENE-9921:
-------------------------------

I'm not sure if this is the best place (perhaps a new issue would be better?), but ICU is at version 70.1 since a few weeks. It'd be nice if the upcoming Lucene 9 does have the latest ICU, whether you integrate it via this proposed change or not :)

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org