Home/ Questions/Q 4622098
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T02:47:45+00:00

When sharing a project with team members through version control, it is customary to

  • 0

When sharing a project with team members through version control, it is customary to include the .project in the source under version control. This makes sure that others on the team get all the dependencies and resources for the project. But the .project uses full/rooted paths to the resource, and not all members of a team will be working in the same environment. Even if all the members are on the same platform, the paths can often be in the user’s home directory.

For the .classpath file, we can get around this problem by using build path variables. Each member defines the path to location of dependent libraries on their system, and the .classpath only refers to the variable.

This is a particular concern for Grails project – when we add a plugin, it updates the .project accordingly.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    General Approach

    As others have mentioned, you should not keep the IDE files in VCS, you should keep an IDE-agnostic description of the project in VCS and generate the IDE-specific project files from them.

    Java-Maven Example

    Keep the pom.xml file(s) in VCS and generate the Eclipse files by running mvn eclipse:eclipse

    Grails Example

    A Grails project is described by application.properties and grails-app/conf/BuildConfig.groovy. These files are present in every Grails application. You can generate the Eclipse project descriptions from them by running:

    grails integrate-with --eclipse

    This command also supports other tools such as IntelliJ and Textmate

    • 0