Definitely got my support. maven.log is an easy no-no, and the reasons for having .project and .classpath would only really hold if either:
a) project has all its dependencies in a lib/ b) project assumes the user will set a MAVEN_REPO variable in eclipse and have the values found there. Neither seems likely to be default for a project, and would constantly see pain caused by accidental committings. Do you want me to take it to the Jakarta PMC? Alternatively we could just float the idea on Jakarta General and Maven Users/Dev and see what happens. Also, as Eclipse is not just Java, I assume the .project file is applicable to all projects. Hen On Thu, 14 Aug 2003, Greg Stein wrote: > On Thu, Aug 14, 2003 at 10:49:29PM -0000, [EMAIL PROTECTED] wrote: > >... > > From: Jason Dillon <[EMAIL PROTECTED]> > > Subject: Re: [PATCH] Added maven.log, .project and .classpath into > > .cvsignore > > To: [EMAIL PROTECTED] > > Date: Fri, 15 Aug 2003 05:27:13 +0700 > > > > >Whats the global cvsignore? > > > > CVSROOT/cvsignore > > > > I would have done this, but I do not have access to CVSROOT. > > Well, that wouldn't have been too friendly since the entire ASF shares that > CVSROOT. I would recommend bringing up the change on infrastructure. Maybe > asking the Jakarta PMC or something to see if the entire Java community > would buy off on the additions. > > Cheers, > -g > > p.s. I have access to make the change, but would wanna see some wider buyoff > from the larger community first. > > -- > Greg Stein, http://www.lyra.org/ >
