[ https://issues.apache.org/jira/browse/LUCENE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161940#comment-17161940 ]
Dawid Weiss commented on LUCENE-9438: ------------------------------------- That was my point: autocomplete in such a setup doesn't really work as it'll suggest things that shouldn't be visible on a given subproject's classpath. Also, I know Eclipse can be a pain with multi-project workspaces - this was one of the key reasons I moved from Eclipse to IntelliJ, actually. > 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 > > > 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