Udo Rader <udo.rader@bestsolution.at> wrote on 05/10/2006 04:33:05 PM:
> I don't think that this bugreport is related to my problem, because the
> report is about the log message I really saw in my SVN log _before_
> upgrading to 1.0.1. After the upgrade I don't see it anymore.
>
> But the log message was never my major concern, the real problem is that
> I am no longer able to reliably use subclipse to maintain my projects,
> because the above "internal error" popup appears. I have to disconnect
> the project(s) and reshare them (reusing the still existing .SVN
> directories and files in the project) and then I am able to commit,
> update and so on until I close eclipse and start it again.
OK, but my point was that the .metadata message was fixed in 1.0.1. I do
not know what this other error is that you are talking about, so you at
least need to provide more information about what it is. What is the
message? Stack-trace? Etc..
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed May 10 22:34:59 2006