[
https://issues.apache.org/jira/browse/LUCENE-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444024#comment-17444024
]
Arjen commented on LUCENE-9921:
-------------------------------
I know that.
I even fixated it in my build.gradle at 62.2 to prevent other libraries from
picking a different version... but if another library needs a higher version,
that higher version is apparently selected by Gradle (rather than stopping with
a version conflict). Which I discovered with Antlr; they upgraded from
something below 62.2 to 70.1 in their version 4.9.3 :(
I can stick to 4.9.2 for now, but it would be nice to be able to upgrade in the
semi-near future (i.e. waiting for 9.1 should do).
> 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
