[jira] [Commented] (LUCENE-9438) Add gradle workflow support for Eclipse IDE

["Robert Muir (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LUCENE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161932#comment-17161932 ] 

Robert Muir commented on LUCENE-9438:
-------------------------------------

The single "blob" project isnt a fanboy thing, I don't think anyone "likes" it: it is just a practical thing so that this IDE really works and doesn't choke all the time. As Uwe Schindler mentioned, it is a hack, but it works. A big important thing is keeping the eclipse memory reasonable so you can actually use it and it doesn't OOM. Because when it crashes you tend to lose work, which is really frustrating.

Even with just a single blob project and keeping things minimal, you constantly have to be your own "garbage collector" and be sure to not have too many projects open at once. I always make sure to close unused ones, otherwise it slows down too much and I know it will only crash and cause lost work.

Personally, I use it the same way as Uwe does: as a fancy autocomplete editor (because java is an extremely verbose language). For any other programming language I really just use vim, but for java it is just too painful to e.g. type in every {{import}} statement manually or rename things :) Running build and tests, git operations, etc: I do all this stuff from the commandline. From Uwe's comments, I think he uses a similar strategy.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org