iamsanjay commented on PR #2643: URL: https://github.com/apache/solr/pull/2643#issuecomment-2286334024
``` * What went wrong: Execution failed for task ':solr:prometheus-exporter:analyzeTestClassesDependencies'. > Dependency analysis found issues. usedUndeclaredArtifacts - org.apache.solr:solrj-zookeeper:10.0.0-SNAPSHOT@ * What went wrong: Execution failed for task ':solr:modules:gcs-repository:analyzeClassesDependencies'. > Dependency analysis found issues. usedUndeclaredArtifacts - com.google.auth:google-auth-library-credentials:1.23.0@jar * What went wrong: Execution failed for task ':solr:modules:hdfs:analyzeClassesDependencies'. > Dependency analysis found issues. usedUndeclaredArtifacts - io.dropwizard.metrics:metrics-core:4.2.26@jar * What went wrong: Execution failed for task ':solr:modules:s3-repository:analyzeClassesDependencies'. > Dependency analysis found issues. usedUndeclaredArtifacts - software.amazon.awssdk:http-client-spi:2.26.19@jar ``` I was curious about why these new errors appeared immediately after the upgrade. From the community, I learned that the new changes in gradle-dependency-analyze (as detailed in gradle-dependency-analyze/gradle-dependency-analyze#527) have introduced these warnings. While some of these dependencies seem to be transitive, I cannot see them being directly used in the project. I wonder if there might be another reason for these warnings beyond them being transitive dependencies. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org