[
https://issues.apache.org/jira/browse/LUCENE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17182108#comment-17182108
]
ASF subversion and git services commented on LUCENE-9438:
---------------------------------------------------------
Commit b1e2d0c8906615a4de41511fbd1bd663908b7195 in lucene-solr's branch
refs/heads/master from Dawid Weiss
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b1e2d0c ]
LUCENE-9438: Eclipse IDE support with gradle build system (#1761)
> Add gradle workflow support for Eclipse IDE
> -------------------------------------------
>
> Key: LUCENE-9438
> URL: https://issues.apache.org/jira/browse/LUCENE-9438
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Major
> Attachments: capture-1.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Off the top of my head I've tried using the eclipse plugin (this should
> prepare "static" classpath entries pointing at local gradle caches). It
> almost works... almost because we have references between sub-atomic project
> elements (tests and main) that make Eclipse see these as circular (because
> Eclipse treats project sources and main classes as one).
> I pushed this code to jira/LUCENE-9438. Perhaps there are ways of making it
> work. I'm not a big fan of having a single "blob" project with all the
> sources and classpaths combined (the IDE won't help you figure out what's
> accessible from a given subproject then) but maybe it's the only way to make
> it work for Eclipse, don't know.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
