Pretty much everything you need to build your project, including.
Pretty much everything you need to build your project, including: . Project and . Classpath (yes, you should definitively add them, provided the .
Classpath doesn't include any absolute path: any other Eclipse users who would access your versioned project will thank you for that) . Settings content (for project Eclipse specific settings) other build-related files (like a pom. Xml, if you have one) launcher configuration (again, if you have some) Nothing that is generated (like the directory 'gen', or 'bin') should be added to source control Workspace Eclipse metadata shouldn't be versioned either.As I said in "Do you keep your project files under version control?
", the goal is to ease and quicken the project setup process when checked-out in a workspace: "Load it up, set it up, go.
Should I really add . Project? Isn't it specific for every user?
I don't need to add files from gen and bin right? – gruszczy Sep 16 '10 at 10:32 @gruszczy: I have updated my answer to address your question – VonC Sep 16 '10 at 10:34 Ok, that helps. But how about those:?.
Settings/org.eclipse.jdt.core. Prefs and default. Properties?
And how the hell am I supposed to determine on my own, which files I am going to need? – gruszczy Sep 16 '10 at 10:37 @gruszczy: . Settings is the second item on my list (I have added a link on it for you to review).
Don't worry, simply all all its content. If somehow that introduce settings that are too local, you will be able to remove them later. – VonC Sep 16 '10 at 10:43 OK, thanks a lot :) – gruszczy Sep 16 '10 at 10:45.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.