|
Re: what eclipse files to add to repo? [message #877306 is a reply to message #877127] |
Sat, 26 May 2012 11:47 |
R Shapiro Messages: 386 Registered: June 2011 |
Senior Member |
|
|
To share project structure in a reasonable way you need the Eclipse meta-data files. For Java/Android, C++ and Python that would include at least .project, .buildpath, .cproject, .pydevdevproject, and .springBeans (if you're using Spring). Also files in the .externalToolBuilders directory, if you have any of those. I'm sure there are others I haven't run into yet.
Almost always it's also a good idea to share files in project .settings directories (you can handle user-specific settings in the workspace preferences). Similarly .launch files for Eclipse launchers.
It's always a good idea to share .gitignore in my opinion, whether or not you're working in Eclipse. You don't need these to import a project but it makes it far less likely that someone will accidentally add other files that shouldn't be under version control.
None of these are site- or platform-specific as far as I know. In general the site- and platform-specific aspects of Eclipse are handled at the workspace level, not the .project level. Similarly things like user libraries, classpath variables, string substitutions etc -- those are all workspace settings, not project settings. Workspace contents should never be under version control. This is yet another reason to keep workspace directories completely separate from project directories.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03008 seconds