[
https://issues.apache.org/jira/browse/SOLR-14647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17214802#comment-17214802
]
Robert Muir commented on SOLR-14647:
------------------------------------
I think i figured out where it comes from at least when it happened in my case.
My problem is that I used the eclipse gui to modify the eclipse "build path" (I
added missing-doclet sources to hack on it). After doing this, eclipse changes
.classpath to add the new entry, which is fine.
Then later, after a successful compile, it seems to ensure whatever output
folder you configured is added to .gitignore and will modify .gitignore. In my
case it wasn't {{bin}} but something else, but it explains how it happened.
> 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
