[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] An internal error occurred during: "SVN Update".

From: Udo Rader <udo.rader_at_bestsolution.at>
Date: 2006-05-10 22:33:05 CEST

On Wed, 2006-05-10 at 16:14 -0400, Mark Phippard wrote:
> Udo Rader <udo.rader@bestsolution.at> wrote on 05/10/2006 04:13:08 PM:
> > Sorry, to repost on this issue, but after starting up eclipse right now
> > I again get the "internal error" popup when I try to update any project
> > under svn control.
> >
> > So obviously the upgrade to 1.0.1 did not fix my problem ...
> OK, but the error has to be somewhat different because in 1.0.1 we
> hard-code to ignore the .metadata folder.
> Here is an open issue for a similar problem.
> http://subclipse.tigris.org/issues/show_bug.cgi?id=491


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.

Udo Rader

BestSolution.at EDV Systemhaus GmbH

Received on Wed May 10 22:33:24 2006

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.