About a week ago, I got it sorted out that:
- * .iml and *.ipr files were project wide and could go into source control
- *.iws manages workspace settings specific to a user so shouldn't go into source control
Just downloaded Idea9 and I'm faced with the '.idea' directory.
From the documentation
Directory-Based Format project is defined by the .idea directory, located in the project root, and *.iml files. As in the standard format, *.iml files serve to describe modules. The project and workspace settings are stored in a number of XML files under the .idea directory. This allows to avoid merge conflicts when the project settings are stored in a version control system and modified by different team members. Each xml file is responsible for its own set of settings, that can be recognized by its name: compiler.xml, projectCodeStyle.xml, encodings.xml, vcs.xml etc. Thus, for example, adding a new run\debug configuration and changing encoding will affect different xml files.
That's all very well, but it doesn't really explain what should and shouldn't go into source code control.
Is there a one-to-one mapping of what was in the *.ipr, *.iws files with the new files?
Is './idea/workspace' the only one that shouldn't go in source control?
Any help would be appreciated.