[
https://issues.apache.org/jira/browse/LUCENE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444792#comment-17444792
]
Dawid Weiss commented on LUCENE-9921:
-------------------------------------
[~rmuir] do you remember why there are two different versions of icu in
icu.gradle?
{code}
icu_62 "com.ibm.icu:icu4j:62.2"
icu_68 "com.ibm.icu:icu4j:68.2"
{code}
They are both used but I'm not sure why we use two different versions here.
> 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
