You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "James Dyer (Jira)" <ji...@apache.org> on 2020/07/13 19:06:00 UTC
[jira] [Commented] (SOLR-14647) Importing Gradle Projects into
Eclipse pollutes checkout
[ https://issues.apache.org/jira/browse/SOLR-14647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156920#comment-17156920 ]
James Dyer commented on SOLR-14647:
-----------------------------------
I suppose perhaps everyone else has migrated away from eclipse, but perhaps this is invalid and I am doing it wrong?
> Importing Gradle Projects into Eclipse pollutes checkout
> --------------------------------------------------------
>
> Key: SOLR-14647
> URL: https://issues.apache.org/jira/browse/SOLR-14647
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Build
> Affects Versions: master (9.0)
> Reporter: James Dyer
> Priority: Minor
> Attachments: SOLR-14647.patch
>
>
> Switch to master branch, then open Eclipse IDE and select "file > import > existing gradle project" to import lucene/solr. Afterwards, "git status" shows unstaged ".project", ".classpath", ".settings" and "bin" files/directories.
> Adjust the .gitignore file to correctly filter these out.
--
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