Generation of the various IDE-specific project files from a single source of truth would get my vote. :-)
Kind Regards, John Fallows. On 6/24/05, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > On Fri, 24 Jun 2005, James Mitchell wrote: > > > I know I don't have a vote here ;) but if I did, it would be -1 > > I too would be -1, but for a different set of reasons. > > 1) Anyone not using Eclipse will break the Eclipse build any time they > make a change to the dependecies. You can't expect people to update IDE > specific files if they don't use that IDE. > > 2) Sharing these files almost invariably requires each user to set up > project and workspace variables. Either this quickly gets complicated, or > the user has limited flexibility in how to configure their system. Also, > the workspace variables can interfere with other projects. > > 3) It doesn't scale. Someone has already suggested doing the same thing > for IDEA. What about NetBeans, JBuilder, JDeveloper, WSAD, CodeWright, > MultiEdit, ...? Where do you stop, and how do you maintain them all? > Someone coming to project for the first time will expect them to work if > they're there. > > -- > Martin Cooper > > > > 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- > >> > >> > >> > > > > > > >
