Search code examples
javaeclipsesvnversion-controlsubclipse

How to avoid configuration issues working on the same project from different workstations


I'm working on a project stored on a SVN server. I always work on this project from my main workstation, but now I neet to checkout the project from my notebook.

I installed everything it's needed on my new development environment: Eclipse IDE, JDK, Apache Tomcat.

Now when I checkout my project I get some problems: the JRE is not binded to my local virtual machine, and the targeted runtime server (Tomcat) is not found.

I solved this simply configuring the project to the new environment, but obviously when I'll commit changes, I'll have to reconfigure all these parameters to the original environment.

So, is there a way to solve this? Should I avoid committing the whole Eclipse project and store in the server just the source code? Which is the correct way to work? Which files/directories should I remove from version control? JRE + Server settings are in .classpath file. Should I exclude this file from version control?


Solution

  • I take it you're using Eclipse?

    You should not be storing .classpath in your Subversion repository. If I remember, this stores the absolute directory names of the classpath. This will vary from system to system.

    Delete .classpath from your repository, then put an svn:ignore property on your project's root directory (where .classpath is stored) and add to the ignore list the file .classpath.

    This way, others will not accidentally add back in the .classpath file.