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

Re: [Subclipse-users] NPE on team synchronization Subclipse 1.0.1

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-05-31 21:08:16 CEST

Richard Brown <richard.brown@acm.org> wrote on 05/31/2006 03:03:17 PM:

> Subclipse is configured to use JavaSVN.
> For one out of about 20 projects, I get the following "Errors have
> occurred while calculating the synchronization state for
> SVNStatusSubscriber." Details on the error are simply multiple "An
> internal error occurred .." NullPointerException.
> On the Synchronize view, selecting "Reset View" will again get a NPE.
> Using TortoiseSVN on the working copy showed a large number of files had

> never been put into the WC when the project was originally checked out
> from the repository several days and multiple Eclipse restarts ago.
> After TortoiseSVN completed the update and Eclipse was restarted (and
> yes, before the restart Subclipse continued to give NPEs), the NPE no
> longer occurred. So WC was likely in an inconsistent state when
> Subclipse got the NPE.
> It would be nice if detecting the inconsistency and updating to obtain
> the missing files could have been done within Subclipse.

There is not really any information here that could help us fix anything.
If you think you know what caused the problem then please try to supply a
specific reproduction recipe along with the stack trace from the

You likely could have done Team -> Update if there were missing files.
That just fires off the svn update process. Synchronize has to do a lot
more than that.



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 31 21:08:31 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.