Hi, I personally think, that committing those files would not be a good idea, because:
(1) they may be generated automatically by maven (2) many people will modify the files while working - so you will always have to crosscheck and take care before checking in (3) how about those not using idea but eclipse, jbuilder, netbeans, etc. ? should we also commit those files ? Before maven we used to commit the project files, too. But then we were never quite happy because, there were unintented committals or other strugles - one time we committed templates but always forgot to adapt them. Hence, I am really happy with having maven to generate the files for me today. It also gives better consistency. Just my $.02. Regards Felix On 9/17/06, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
On Sunday 17 September 2006 10:32, [EMAIL PROTECTED] wrote: >Log: > Set the svn:ignore property. > +*.ipr > +*.iml Isn't there quite a lot of people using Idea around here. Would be really convenient to have the project and module files committed, especially if the dependencies are referenced via a M2_REPO variable to the Maven2 local repo/cache. Cheers Niclas
