I don't view this as problematic at all. It's not a 'burden' to check in changes to this file since the IDE automatically adds them to the commit list if they have changed.
The IDEA project files represent project-wide settings, and should be shared among everyone who uses IDEA. The IDEA .iws (workspace file) represents what files you are currently viewing, IDE-instance-specific things and should NOT be checked into an SVN. That is why the IntelliJ team separated this stuff into different files - to explicitly allow team-wide sharing of the exact same project configuration, but let workspace-specific things be private. Similarly, I have no problem having project-wide Eclipse files being in the project either. Now if it is a burden for people to manually check those files in after a change (unlike IDEA), then feel free to remove them if you don't want to maintain it. But I don't think it is something you must impose on everyone. Granted, if our build auto-generated them, then I wouldn't care. But currently it doesn't, so I do :) Cheers, Les On Mon, Jan 5, 2009 at 7:20 AM, Emmanuel Lecharny <[email protected]>wrote: > Jeremy Haile wrote: > >> I'd be happy to work on improving the project files so that they work >> out of the box. Could you be more specific as to what problems you've >> encountered? >> >> Having the project files in SVN is very convenient since changes to the >> project are automatically updated for everyone. There are multiple >> committers who use IntelliJ and find these files convenient. >> >> > It's way better to let the build tool generate those files. It keeps the > project consistent, as you don't commit anything relevant to your own env. > > My own experience was that, at first, I thought too that it would be a good > idea to keep those files into svn (for the very same reasons you gave), but > after a few months, it proved to be a real burden, as you had to commit it > every time you did a modification, or more problematic, you are tied with a > set of configuration that does not fit your need. Then I realised that it > was not a good idea to store those files in svn, and was way more convenient > to let the build tool generate them for you. > > > -- > -- > cordialement, regards, > Emmanuel Lécharny > www.iktek.com > directory.apache.org > > >
