Re: [Menda-developers] On tracking Eclipse-related goodies in CVS

[Alex R. <al...@gu...>]

For me the question is more whether or not we want to track project's
meta-information in CVS. As far as I know most of us are using Eclipse
for development at the moment, but what if some other developers would
prefer to use some other IDE (IDEA, NetBeans). What if with future
releases of Eclipse the format of Eclipse's own configuration files
would change?

Still, I'm perfectly fine with:

a) Having Eclipse's files checked-in and tracked in CVS as long as any
local changes I make wouldn't show up in Team Sync perspective (so you
can, say, commit all the changes without going file-by-file excluding
.classpath and .project)

b) Not having Eclipse's files checked-in and making local changes
whenever the libraries are changed (I'm building using ant anyways)

On related subject: our current .classpath contains way too much
libraries for the project to be buildable from inside Eclipse. Why is
stuff like JDBC adapters etc is in there? I'm attaching a minimalistic
.classpath that works OK from Eclipse (you have to have TOMCAT_HOME
defined) and it's almost twice as short as the current one.

Sorry for starting a flame war <ducks> :)

Regards,
  Alex