+1 for Bill's suggestion to check them in. I've dealt with the same issues here and there are pros and cons in both, but overall I think there are more benefits in checking them in. Yes, Eclipse would touch those, but if everybody has the same settings they'd remain the same. If you want to use your own settings, just create your own project a level above and use your own .projet and .classpath. Naturally you don't have to use them if you don't want to. But it's the same thing as with Oliver's keep libs checked in -argument (which is another thing where there are both pros and cons, it's not automatically just good or bad); making it possible to just import a project into your Eclipse workspace is a whole lot easier for new people who are evaluating MyFaces (and hopefully contributing to the project later) than letting them figure out required libs and source paths all by themselves.
Kalle > -----Original Message----- > From: Bill Dudney [mailto:[EMAIL PROTECTED] > Sent: Friday, June 24, 2005 10:47 AM > To: MyFaces Development > Subject: Re: Eclipse .project & .classpath files (is he > talking about Maven again?!?!?!) > > Hi James, > > Thanks for the feed-back. Good point about Eclipse touching > the files. Other option is putting the files into a > subdirectory as we used to have them. Also I could just post > them on the wiki as you are thinking of doing with the POM. > > My issue with maven is upkeep. If we have the ant build that > everyone else is using and a POM for maven that only some are > using there will be stuff that goes stale. > > Getting a maven generated .project & .classpath is a major > win of using maven agreed. I believe the maven/ant discussion > has been beaten to death on this list though and I for one > don't want to open that up again ;-) > > TTFN, > > -bd- > > On Jun 24, 2005, at 11:41 AM, James Mitchell wrote: > > > I know I don't have a vote here ;) but if I did, it would be -1 > > > > Best case > > --------- > > By doing this, you are forcing every developer to deal with files > > that will always appear to have changes/differences. Yes, Eclipse > > will touch those files. > > > > In most projects that I've been involved in. You generally > want to > > ignore those files because they assume a certain IDE is being used > > by all. > > > > > > Worst case > > ---------- What do you propose someone do if they need that spot > > (i.e. they are using a different IDE and different format, which > > requires a ".classpath" file in the place of the one under svn)? > > > > > > Let's meet in the middle > > ------------------------ > > Not to beat the Maven drum any more than I have to....but that's > > actually one of the cool features of Maven. With a proper Maven > > project.xml file describing dependencies, creating the .project > > and .classpath files for *any* IDE is as simple as... > > > > http://maven.apache.org/reference/plugins/eclipse/ > > http://maven.apache.org/reference/plugins/idea/ > > http://maven.apache.org/reference/plugins/jbuilder/ > > > > > > ...ah shucks, take your pick... > > > > http://maven.apache.org/reference/plugins/index.html > > > > > > FYI - I will be Mavenizing the MyFaces build within the > next couple > > of weeks. Whether it is accepted into SVN is another issue for > > another thread. If not, I will make it available somewhere (wiki, > > docs, something). > > > > > > -- > > James Mitchell > > Software Engineer / Open Source Evangelist > > Consulting / Mentoring / Freelance > > EdgeTech, Inc. > > http://www.edgetechservices.net/ > > 678.910.8017 > > AIM: jmitchtx > > Yahoo: jmitchtx > > MSN: [EMAIL PROTECTED] > > Skype: jmitchtx > > > > ----- Original Message ----- From: "Bill Dudney" <[EMAIL PROTECTED]> > > To: "MyFaces Development" <[email protected]> > > Sent: Friday, June 24, 2005 1:05 PM > > Subject: Eclipse .project & .classpath files > > > > > > > >> Hi All, > >> > >> i'd like to supply an Eclipse configuration for the > projects that > >> Sean is currently working to get set up in SVN. The projects > >> would work assuming the dependencies are downloaded via > >> 'download- dependencies'. That would get someone up and running > >> easily in Eclipse. I'd like to put these files under each of the > >> subprojects (i.e. api, impl, etc.) and under the projects > >> (current, tomahawk etc.) > >> > >> So, once you download one of the projects you could define a > >> variable and run 'ant download-dependencies' and you'd have a > >> ready to go MyFaces project in eclipse. > >> > >> Thoughts? > >> > >> TTFN, > >> > >> -bd- > >> > >> > >> > > > > > > >
