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

Dawid Weiss commented on LUCENE-9438:
-------------------------------------

I really am IDE-agnostic, I don't care. I use what works, including vi. 

Generating global .classpath should be relatively easy; snippets that may be 
helpful here:

Collect sourcesets from all java projects:
{code}
            if (project.plugins.findPlugin(JavaPlugin)) {
                [
                    project.sourceSets.main.java.srcDirs,
                    project.sourceSets.test.java.srcDirs,
                ].flatten().each { srcLocation ->
{code}
Source folders should have per-location outputs (in case the same class is 
duplicated in multiple source locations).

To collect (resolved) dependencies - there are bits and pieces in 
jar-checks.gradle that should be relevant.

After that it's about deduping and generating .classpath; maybe manually 
filtering some stuff. 

Should be doable, but some trial and error is definitely in order.




> 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

Reply via email to