> You are correct that to take advantage of the feature you do have to
> checkout again in order to get Subversion to set the timestamps. But
> that does not mean an existing working copy would not work, it just
> would not have the timestamps you want.
> I think this was a coincidence. Subclipse is not going to crash
> because of anything in that file. I also do not think that stack
> trace you sent had anything to do with Subclipse.
I have written 2 mails with different content. Let me write a few more
words:
My firrst mail states, that subclipse throws an exception, when the
property in the subversion config file is not correct (beginns with an
blank) I have not send the exception.
My second mail states, that i have had problems with my eclipse
workspace (after the property was corrected) I was not able to start
eclipse anymore. The exception shown is the npe i got when starting
eclipse with -debug.
Solution for me was: setting the property to false and recreating a new
workspace. I am able to work with eclipse, again.
I copied my working workspace and tested it. Now the property was set to
true again. But eclipse won't start, again with the mentioned exception.
Hope all is clear now. Subclipse is not to blame.
But it seems that eclipse has some problems with this feature (history?)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Thu Feb 22 15:01:04 2007