Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I've been using eclipse for a long time to do development. One of the problems I've come across when working on other people's projects is if they come from source control, some of the eclipse project files "default.properties" and other xml config files are missing. Its usually a big pain in the butt to get the project running in eclipse. I understand the reasoning to not have certain files tracked because they may be full of specific stuff to a certain eclipse install. How do all of you manage that?

share|improve this question
add comment

2 Answers

up vote 7 down vote accepted

My solution has always been to not check those files in.

I really have never liked it when I do a check out and have to filter through all the IDE-specific stuff. Why not use a common ground? If the IDE files are the common ground, great. But, more often than not, something like Ant and Maven are the common ground.

It depends on the audience, but I generally avoid it. Build tools are mostly universal, and IDE's fall near the edge of the text editor religious wars. I'm a peaceful guy and practice my religion in private.

share|improve this answer
    
+1 for recommending an external project management tool. Specifically Maven. –  TheLQ Jan 5 '11 at 3:48
    
So I guess I'm confused. Are you suggesting to use Maven for the project? –  Matt Phillips Jan 5 '11 at 3:49
1  
+1 put this stuff into your .gitignore or svn ignore properties. This way if two team members have different versions of an IDE it's not a problem. –  Keyo Jan 5 '11 at 3:51
1  
@Matt: I am saying if many people and automation scripts need to run and build the project in many different environments, then it's a good idea use a more universal build tool not directly tied to an IDE. –  Jeremy Heiler Jan 5 '11 at 3:52
add comment

I would typically check those files into source control. It's usually best to check in everything you need so that you can simply check out a fresh copy, fire up your IDE and build.

It's slightly different if people are using heterogeneous IDEs and build tools (e.g. if some people are using Eclipse and some are using NetBeans) but that's a situation I'd generally try to avoid.

share|improve this answer
    
That's the nice thing about doing android projects (which is what prompted my question). Only 1 IDE to manage so its not as big of a deal to do it. –  Matt Phillips Jan 5 '11 at 3:48
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.