Home/ Questions/Q 8716381
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T06:03:57+00:00

I’m used to other IDEs such as Visual Studio which keep project structure on

  • 0

I’m used to other IDEs such as Visual Studio which keep project structure on some metadata files. I’m using Eclipse right now and I used m2e eclipse to import a maven project. afaik Eclipse only gets source/resource files from pom.xml (or maven default directories if none is specified) and create the project tree.

Therefore, i think that, if I have the code and Eclipse configuration files (.project, .classpath) in a repository and I update code directory structure, no Eclipse files will be updated and therefore I don’t need to update Eclipse files in the repository.

Is that correct?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Generally, if you use m2e (recent versions) and a SCM (Git, Svn, CVS, etc.), you don’t need to commit the Eclipse configuration files to the repository.
    These main files are :

    • .project
    • .classpath
    • .settings/

    There is a good example on GitHub of a .gitignore file which shows what files in Eclipse you don’t need to commit.

    EDIT :

    To regenerate Eclipse project files, you can either :

    1. Import > Existing Maven Projects : needed eclipse files are created

    2. Import > Checkout Projects from SVN (or CVS, GIT, etc.) ….. if needed : Convert to Maven project

    3. Use CLI maven-eclipse-plugin with mvn eclipse:eclipse (Goal) (not recommended if using m2e)

    • 0