Permalink
Browse files

Ignore '.project' and '.classpath' to avoid conflict between developm…

…ent environments.
  • Loading branch information...
1 parent 1a188f2 commit 3ad9edaa260b62de4177dae060bda0ecfcbc3ff0 @allonhadaya allonhadaya committed Apr 11, 2012
Showing with 4 additions and 0 deletions.
  1. +4 −0 Android.gitignore
View
@@ -14,3 +14,7 @@ gen/
# Local configuration file (sdk path, etc)
local.properties
+
+# Eclipse project files
+.classpath
+.project

2 comments on commit 3ad9eda

This may be a silly question but how can I import a project into a new Eclipse workspace if the project files are not committed? If I add new source folders to the build path, how do I indicate that to the rest of my team?

Contributor

allonhadaya replied Feb 2, 2013

As far as new workstations go, clone the repository and import the project as shown here.

As long as the new folders are in one of your current source folders, eclipse should pick it up when you refresh. For new source folders have your teammates add them manually. -- source

At the end of the day, pick whatever is best for your project and team. If you don't experience conflicts in the .project or .classpath between environments, feel free to remove those entries from your gitignore and push changes up. Otherwise you might have to pay the price by importing and maintaining file structure manually.

Please sign in to comment.