You are correct about the sometimes :)
To keep it short : they are a PITA.
To make it a little bit longer : I always run into .classpath conflicts and I don't like that other
people dictate how my eclipse should behave and which version I should run and I don't expect others
to have to put up with the .classpath and .project files I am using.
In my opinion it's good practice to add them to cvsignore or svn:ignore, with a possible exception
when you are in control of everyone elses environment, which is clearly not the case here.
And you can just type maven eclipse to get a nice .classpath and .project..
Mvgr,
Martin
Dion Gillard wrote:
Any reason you want to ignore the eclipse files?
Sometimes it makes checking the project out from Eclipse a whole load easier.
On 2/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Author: mvdb
Date: Tue Jan 31 15:49:34 2006
New Revision: 373946
URL: http://svn.apache.org/viewcvs?rev=373946&view=rev
Log:
ignore eclipse files and target directory.
Modified:
jakarta/commons/sandbox/csv/trunk/ (props changed)
Propchange: jakarta/commons/sandbox/csv/trunk/
------------------------------------------------------------------------------
--- svn:ignore (added)
+++ svn:ignore Tue Jan 31 15:49:34 2006
@@ -0,0 +1,3 @@
+.classpath
+.project
+target
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
http://www.multitask.com.au/people/dion/
"In order to succeed, your desire for success should be greater than
your fear of failure." - Bill Cosby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
