On Wed, 2006-05-10 at 16:34 -0400, Mark Phippard wrote:
> Udo Rader <firstname.lastname@example.org> 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..
Hmm, ok. I had hoped to have explained it sufficiently in my original
post, but anyhow, I will try to explain more in detail:
For a couple of days now I have major problem with my setup.
Whenever I try to update one of my SVN shared projects by right clicking
on the project name/a resource and then "Team"->"Update" a popup opens
that contains the following message: 'An internal error occurred during:
The only way to the it working again is to right click on the project
name, then Team->Disconnect and choose "Do not delete the SVN meta
After disconnecting the project I can immediately right-click on the
project name again and choose "Team"->"Share Project", choose "SVN" as
the repository type, then "Next". In the following window I am told that
the project is already shared and the information is indeed correct, I
see the correct repository URL. "Validate connection on Finish" is also
activated. If I then click on "Finish" this project is accessible via
SVN again and I can right-click on any Resource and perform a
Team->Update or Team->Commit on it.
Yet after shutting down eclipse and restarting it, the project becomes
inaccessible via SVN again and I get the error popup mentioned above.
As per a stack trace, how would I get such a thing under Linux?
Subclipse or whatever component does not segfault and so I don't get any
coredump and thus cannot provide you with any tracing information.
BestSolution.at EDV Systemhaus GmbH
Received on Wed May 10 22:52:39 2006