You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/08/21 19:48:00 UTC

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

     [ https://issues.apache.org/jira/browse/LUCENE-9438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dawid Weiss resolved LUCENE-9438.
---------------------------------
    Fix Version/s: master (9.0)
       Resolution: Fixed

> 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
>             Fix For: master (9.0)
>
>         Attachments: capture-1.png
>
>          Time Spent: 20m
>  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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org