Removed IDE specific files like .project and .settings

[ujovlado]

IDE specific files should not be in repository. When someone else using same IDE, you can break your settings each other by commiting these files.

I've added some of them to .gitignore and also deleted from repo.

[Sammaye]

Indeed these files should be removed, I gotta change how eclipse takes my project from git first though, whenever I get eclipse to make a new project from git it always breaks hence the reason why I have never removed them yet since I can just pull the project striaght down without the hassle.

Could switch IDE but Eclipse just works, well.

[Sammaye]

Could easily remove the .settings right now, they are not needed.

[Sammaye]

Removed the .settings, just gotta figure out how to remove the .project, though it is just a small file maybe it is ok to leave that in if it makes life a bit easier when dealing with eclipse?

[ujovlado]

It's only cosmetic change. The main aim of this is not remove them and affect your workflow, IDE or something. Important is to have files of this type ignored - avoid commitiing.

On your machine you should keep them. ;)

For example, I have an .idea directory in the root of repo and .gitignore never let me commit any file in it (sure, if I want, I can do it).

So my opinion is:

• make a backup of these files
• apply these "patch" (if you want of course)
• copy them back

[Sammaye]

Yeah, the only problem at the moment is that the reason I commit it (.project) is so that I can logon to any computer, pull the repo and instantly be off without backing up my files to dropbox or another repo or something like that.

So even though it is a comestic change for where the repo is already checked out, for new computers it isn't which is where the problem starts. Checking out a uninitalised repo in eclipse is painful to say the least, it's the only part of eclipse which doesn't work, but it doesnt work really well to the point of making you scream.

Maybe this feature has improved with updates so that I can ignore them, I will need to look into that.

[ujovlado]

Unfortunately, is not possible to have file commited in repository and disabled cloning of it (doesn't matter if is in .gitignore or not).

[Sammaye]

That is one feature I dislike over SVN :)

I'll take a look at updating my eclipse and EGit

[ujovlado]

Yes, I understand. I don't want to affect your workflow or something. I'm not using Eclipse, so actually haven't problem with these files.

Solution can be have these files on some dev branch and deleted on master.

[Sammaye]

Yes, then each time I just make a pull request from dev to master, that is definitely a method.

[ujovlado]

Thx 👍
And how did you solve problem with .project file?

[Sammaye]

I took the dive in the end removing it from my workflow. I tested it today and it seems Eclipse now wants to checkout my project first time around and actually work, for the moment. So I am gonna just handle this one, if the bugs in EGit come back to bite me then I have other projects from which to copy a .project from :).