[
https://issues.apache.org/jira/browse/SOLR-17406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912314#comment-17912314
]
Christos Malliaridis commented on SOLR-17406:
---------------------------------------------
[~ichattopadhyaya] so I had a look into this and because I never used Eclipse
before, I am not sure how the project is supposed to look like. I am also not
sure how a typical gradle project is supposed to be opened / imported, so I
tried the following two approaches:
Approach 1 - Using "gradlew eclipse":
# Before opening project in Eclipse, run ./gradlew eclipse (works only on 9.x
branches)
# Open Eclipse, then go to File -> Open Projects from File System -> Select
solr project where gradlew eclipse was executed
This approach resulted in the following view:
!Screenshot 2025-01-13 012825.png|width=106,height=235!
Aproach 2 - Using "Eclipse Gradle (buildship) tooling" (see
[https://www.vogella.com/tutorials/EclipseGradle/article.html)]:
# Open Eclipse and go to File -> Import...
# Under Gradle select "Existing Gradle Project"
# Select the project root directory
# Continue with Next until Eclipse starts analyzing the project
# After it identifies the Solr project, click finish
This approach works with main (clean checkout) as well and it also identifies
correctly the gradle tasks without even building the project. The result would
look like this:
!Screenshot 2025-01-13 014721.png|width=262,height=194!!Screenshot 2025-01-13
014818.png|width=136,height=197!
If the latter approach is sufficient and developers can work with that, we can
probably remove gradle/ide/eclipse.gradle and update our documentation to only
use the IDE features, instead of relying on a gradle plugin.
P.S. I had to run "gradlew dev" once from terminal, because it was for some
reason failing on solrj spotless stuff when I tried to execute the same gradle
task fromt he tasks window.
> 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
> Attachments: Screenshot 2025-01-13 012825.png, Screenshot 2025-01-13
> 014721.png, Screenshot 2025-01-13 014818.png
>
> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
