[
https://issues.apache.org/jira/browse/SOLR-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912284#comment-17912284
]
Ishan Chattopadhyaya commented on SOLR-17406:
---------------------------------------------
As I re-read Christos' comment in dev@ list, this may have happened
inadvertently.
I'm looking at the fix, based on his suggestion:
{quote}
Could you check if reverting the "wrapping" (line 24 in
gradle/ide/eclipse.gradle) of the eclipse-related part resolves the issue?
See the changes in eclipse.gradle from
https://github.com/apache/solr/commit/c9d3885f2fd0a7edf5efe4a264d0bdc276109eba
{quote}
> Introduce Gradle Version Catalogs
> ---------------------------------
>
> Key: SOLR-17406
> URL: https://issues.apache.org/jira/browse/SOLR-17406
> Project: Solr
> Issue Type: Improvement
> Components: Gradle
> Affects Versions: main (10.0)
> Reporter: Christos Malliaridis
> Assignee: Christos Malliaridis
> Priority: Minor
> Labels: dependencies, gradle, pull-request-available
> Time Spent: 8h
> Remaining Estimate: 0h
>
> With Gradle it is possible to manage versions and dependencies in gradle
> files via version catalogs. This allows us to cleanup dependency resolution
> and move various versions from across the project to a single file.
> Dawid Weiss demonstrated in [Lucene PR
> #13484|https://github.com/apache/lucene/pull/13484/] such a migration
> together with a few improvements in the gradle build files that could be
> addressed in this ticket aswell.
> The migration include the removal of palantir's consistent versions plugin.
> Dev list thread:
> [https://lists.apache.org/thread/wh6c0x2ncbpd61pwwddtv3l256lv9kr5]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
