Oops - yeah, I forgot about that. Very useful stuff indeed. On Mon, Jan 5, 2009 at 8:45 AM, Jeremy Haile <[email protected]> wrote:
> On Jan 5, 2009, at 8:42 AM, Les Hazlewood wrote: > >> Granted, if our build auto-generated them, then I wouldn't care. But >> currently it doesn't, so I do :) >> > > Even if it auto-generated them, it wouldn't auto-generate the items I > mentioned such as file templates, static analysis settings, code style > settings, etc. that can be useful to help ensure code consistency and best > practices. > > > > >> 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 >>> >>> >>> >>> >
