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

Re: Subclipse 0.9.37 ussues on Eclipse 3.2

From: Eugene Kuleshov <eu_at_javatx.com>
Date: 2005-11-03 23:00:08 CET

Mark Phippard wrote:

>> I am running integration build of Eclipse 3.2 eclipse-I20051102-1600
>>and consistently getting the following exception on the synchronization
>>with any repository
>> Do you have any clue what this could be?
>Is there a specific reason you replied to this email? Is this a 0.9.37
>issue? Did not exist in 0.9.36?
>Trying to understand the scope of what you are saying here. AFAIKnew, you
>were having these problems with 3.2 for a while now.
  My bad. I just did two things at once... You are right, he same issue
was on 0.9.36.
  Anyway, I think I found the cause for this issue. I've been
synchronizing workingset that have mix of projects shared in CVS and
SVN. So, it looks like Subclipse is not checking for the team provider
type when including projects into the sync. Once I removed CVS projects
from this set this NPE went away. I think projects that are not shared
with Subclipse team provider should be ignored.

  Also, when I work with Maven's repository at Apache SVN server at
  from time to time I see all kinds of weird errors on both sync and
update. Not to mention that Subclipse very often freeze workbench window
for 10..20 seconds. Can somebody try to get this project to the
workspace and periodically run sync/update and keep an eye on errors? I
just don't know what to think about it...

  By the way. When running synchronize Subclipse is actually start two
jobs (I guess they are nested). Does it suppose to be this way? You can
see these jobs on the progress view in both Eclipse 3.1 and 3.2

Received on Fri Nov 4 09:00:08 2005

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.