IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?

by

We have a FAQ article covering this question.

[The .idea] format is used by all the recent IDE versions by default.
Here is what you need to share:

  • All the files under .idea directory in the project root except the workspace.xml and tasks.xml files which store user specific settings
  • All the .iml module files that can be located in different module directories (applies to IntelliJ IDEA)

Be careful about sharing the following:

  • Android artifacts that produce a signed build (will contain keystore passwords)
  • In IDEA 13 and earlier dataSources.ids, datasources.xml can contain database passwords. IDEA 14 solves this problem.

You may consider not to share the following:

  • .iml files for the Gradle or Maven based projects, since these files will be generated on import
  • gradle.xml file, see this discussion
  • user dictionaries folder (to avoid conflicts if other developer has the same name)
  • XML files under .idea/libraries in case they are generated from Gradle or Maven project

.idea directory is a replacement for the old .ipr (Idea Project) file and if you want to share the project between users, then you need to share .idea folder (with the exceptions mentioned in the FAQ) and all the .iml files.

More Related Contents:

  1. When should you branch?
  2. Why is a 3-way merge advantageous over a 2-way merge?
  3. Using IPython / Jupyter Notebooks Under Version Control
  4. ClearCase advantages/disadvantages [closed]
  5. Should I store generated code in source control
  6. What is the cleverest use of source repository that you have ever seen?
  7. Source control vs. Revision Control?
  8. What’s the best three-way merge tool? [closed]
  9. Storing third-party libraries in source control
  10. Mercurial for Beginners: The Definitive Practical Guide
  11. Named Branches vs Multiple Repositories
  12. Mercurial — revert back to old version and continue from there
  13. Is version control (ie. Subversion) applicable in document tracking? [closed]
  14. Mercurial Subrepos – How do you create them and how do they work?
  15. How to edit incorrect commit message in Mercurial? [duplicate]
  16. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  17. Mercurial: How to ignore changes to a tracked file
  18. How do I perform a recursive checkout using ClearCase?
  19. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  20. Is there a way to keep Hudson / Jenkins configuration files in source control?
  21. Branching Strategies [closed]
  22. Comparison between Centralized and Distributed Version Control Systems [closed]
  23. Can you “ignore” a file in Perforce?
  24. Mercurial: Merging one file between branches in one repo
  25. What is the difference between hg forget and hg remove?
  26. How often to commit changes to source control? [closed]
  27. Do you continue development in a branch or in the trunk? [closed]
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment