Results 1 to 2 of 2

Thread: Why don't you put .classpath files in the repository?

  1. #1
    Join Date
    May 2005
    Posts
    1

    Default Why don't you put .classpath files in the repository?

    Without these files Eclipse gives very strange errors (you have to add "Plug-in dependencies" library on the classpath).

    I've looked at these files and find no developer-specific information, so they can be put in the repository. So what's the reason then?

    Maybe the problem is in the JRE? But you can use the workspace default one in that case.

  2. #2
    Join Date
    Aug 2004
    Location
    Frankfurt/Main, Germany
    Posts
    253

    Default Re: Why don't you put .classpath files in the repository?

    You are right. After dropping support for Eclipse 2 we don't have the problem that the .classpath files are wired to a specific version of Eclipse (plugin version number in classpth) anymore.

    The only problem left is the full path of the source code locations stored in .classpath files. So if I commit my current .classpath files then Mac OS X paths (e.g. "/Users/torsten/Develop/spring-framework-1.1.5/src) are stored within them :-).

    Ok, I will remove the source code locations and commit the .classfiles.

    Cheers,
    Torsten

Similar Threads

  1. Reusable 'Module' configuration files?
    By zanfolim in forum Architecture
    Replies: 6
    Last Post: Sep 28th, 2006, 06:52 AM
  2. Replies: 0
    Last Post: Aug 9th, 2005, 11:49 AM
  3. Replies: 7
    Last Post: Jul 26th, 2005, 02:48 PM
  4. Replies: 38
    Last Post: May 11th, 2005, 02:49 PM
  5. Unexpected behaviour with multiple config files
    By rgitzel in forum Container
    Replies: 7
    Last Post: Mar 8th, 2005, 07:11 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •