Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider removing Eclipse artifacts from project #135

mdgeek opened this Issue Mar 26, 2015 · 2 comments


None yet
3 participants
Copy link

mdgeek commented Mar 26, 2015

The inclusion of Eclipse artifacts (.settings, .project, .classpath) is a bit of a pain when doing pulls as they always trigger a merge. We routinely exclude these from our commits for that reason. This is a gentle request to remove them.


This comment has been minimized.

Copy link

jamesagnew commented Mar 26, 2015

This seems reasonable, we probably should have done so long ago.
In the old days, Eclipse's Maven support was awful and checking in your eclipse files made it a bit less painful to deal with.. but these days that just doesn't seem to be the case any more.


This comment has been minimized.

Copy link

XcrigX commented Nov 21, 2016

I still see .project, .settings, .classpath files/folders sprinkled all throughout the project.

If you do want to attempt to remove them, here is a recipe I follow:

First add/commit any current changes, obviously.

Then update the root .gitignore file, I use to assist generating gitignore files. Pretty handy..

You can use this command to then see the files in the project that correspond to ignored files:
git ls-files -i --exclude-from=.gitignore

And this to remove them from git tracking without removing them from your local disk:
git rm --cached 'git ls-files -i --exclude-from=.gitignore'


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.