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

Chris M. Hostetter commented on SOLR-17917:
-------------------------------------------

Is {{dev-docs/lucene-upgrade.md}} no longer accurate?

I tried update the {{jira/solr-17917-lucene-10.3-upgrade}} branch to 
Lucene-10.3.1, but after making the change to {{gradle/libs.versions.toml}} I 
ran into some kind of Catch-22 ...
 * {{gradlew :resolveAndLockAll}} makes no changes to my repo
 * {{gradlew updateLicenses}} fails because the version is locked to 10.30.0

{noformat}
hossman@slate:~/lucene/solr [j21] [*jira/solr-17917-lucene-10.3-upgrade] $ git 
status
On branch jira/solr-17917-lucene-10.3-upgrade
Your branch is up to date with 'origin/jira/solr-17917-lucene-10.3-upgrade'.

Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        modified:   gradle/libs.versions.toml

hossman@slate:~/lucene/solr [j21] [*jira/solr-17917-lucene-10.3-upgrade] $ git 
diff --staged | cat
diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml
index 4cb51ed3cf3..ffcd84d6cb8 100644
--- a/gradle/libs.versions.toml
+++ b/gradle/libs.versions.toml
@@ -37,7 +37,7 @@ apache-httpcomponents-httpcore = "4.4.16"
 apache-httpcomponents-httpmime = "4.5.14"
 apache-kafka = "3.9.1"
 apache-log4j = "2.21.0"
-apache-lucene = "10.3.0"
+apache-lucene = "10.3.1"
 apache-opennlp = "2.5.4"
 apache-poi = "5.2.2"
 apache-rat = "0.15"
hossman@slate:~/lucene/solr [j21] [*jira/solr-17917-lucene-10.3-upgrade] $ 
./gradlew :resolveAndLockAll

BUILD SUCCESSFUL in 2s
5 actionable tasks: 1 executed, 4 up-to-date
hossman@slate:~/lucene/solr [j21] [*jira/solr-17917-lucene-10.3-upgrade] $ 
./gradlew updateLicenses

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':solr:api:collectJarInfos'.
> Could not resolve all dependencies for configuration 
> ':solr:api:jarValidation'.
   > Could not resolve org.apache.lucene:lucene-test-framework:10.3.1.
     Required by:
         project :solr:api
         project :solr:api > project :platform
         project :solr:api > project :solr:test-framework
      > Cannot find a version of 'org.apache.lucene:lucene-test-framework' that 
satisfies the version constraints:
           Dependency path 'org.apache.solr:api:10.0.0-SNAPSHOT' --> 
'org.apache.lucene:lucene-test-framework:10.3.1'
           Constraint path 'org.apache.solr:api:10.0.0-SNAPSHOT' --> 
'org.apache.lucene:lucene-test-framework:{strictly 10.3.0}' because of the 
following reason: dependency was locked to version '10.3.0'
           Constraint path 'org.apache.solr:api:10.0.0-SNAPSHOT' --> 
'org.apache:platform:10.0.0-SNAPSHOT' (runtimeElements) --> 
'org.apache.lucene:lucene-test-framework:10.3.1'
           Constraint path 'org.apache.solr:api:10.0.0-SNAPSHOT' --> 
'org.apache.solr:test-framework:10.0.0-SNAPSHOT' (runtimeElements) --> 
'org.apache.lucene:lucene-test-framework:10.3.1'

> There is 1 more failure with an identical cause.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s
4 actionable tasks: 4 up-to-date

{noformat}
 

?

> Upgrade to Lucene 10.3
> ----------------------
>
>                 Key: SOLR-17917
>                 URL: https://issues.apache.org/jira/browse/SOLR-17917
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Ishan Chattopadhyaya
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: main (10.0)
>
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Lucene 10.3 is releasing shortly. I think we should upgrade to it before our 
> Solr 10.0 release. WDYT, [~anshum]?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to