[
https://issues.apache.org/jira/browse/SOLR-14647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214445#comment-17214445
]
Robert Muir commented on SOLR-14647:
------------------------------------
I experience the issue as well. And I use only {{gradle eclipse}}. Whenever I
try to hack on the code i end out with eclipse trying to add shit to
{{.gitignore}}. Maybe its caused by me "refreshing" the project. Honestly, the
{{gradle eclipse}} seems perfect, creating the same files as ant did.
I suspect this is an eclipse issue and the easiest fix may be to simply git
ignore {{bin/}} by default. Sure it is dirty but it also follows unix
convention, why would we check in binaries to source code control?
> Importing Gradle Projects into Eclipse pollutes checkout
> --------------------------------------------------------
>
> Key: SOLR-14647
> URL: https://issues.apache.org/jira/browse/SOLR-14647
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: master (9.0)
> Reporter: James Dyer
> Assignee: James Dyer
> Priority: Minor
> Fix For: master (9.0)
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
