Hi folks,
I have few thoughts and questions around this discussion.
How .classpath/.project eclipse files at parent level is a "pain" or
"pollutant"?
I think these files won't even checkout if you just download a specific module.
How does those files are blocking separating out modules OR making
them independent?
I don't think eclipse is being used for this task because without
these files it will be a mess in eclipse, for other editors those
files should not matter.
I think it's very convenient for new folks to have these settings.
These settings give a quick start as most of the people will start
from downloading the whole trunk (unless specified in checkout
instructions).
I can imagine how "not having" these files could be a pain for new folks.
A newbie(with Castor) will go and read the instructions for "svn co"
and after getting that code in eclipse it will be a mess for him/her
as he/she is not familiar with castor's directory structure (or at all
with open source development).
One can imagine the pain to handle questions about setup which will be
thrown by newbies.
If these files is seriously blocking some process then I would say
"YES" go ahead and delete those.
There are many project having project specific eclipse settings to
overcome the bugs of maven-eclipse-plugin or just because it's more
convenient (fast to checkout, less overhead of svn ignore and
generating).
Regards,
Udai
PS: It's more convenient for me to keep those setting (I never use)
which helps someone in my team instead of teaching the other way
around that I use.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
