Mark Phippard napisał(a):
> On 2/7/07, *Grzegorz Kossakowski* <firstname.lastname@example.org
> <mailto:email@example.com>> wrote:
> I'm experiencing some problems elated to Team Synchronizing with
> Subclipse. I have about thirty projects in my workspace all
> checked out
> from remote repository. When I fire synchronization in Eclipse I
> experience following very odd problems:
> 1. I cannot access repository url
> (https://svn.apache.org/repos/asf/cocoon/) via Firefox any longer. How
> it can be that Eclipse/Subclipse blocks whole traffic on this
> All other hosts can be accessed without problem. I even can access
> repository on http protocol instead of https...
> We do not perform the communication in Subclipse, we just invoke an
> API, in your case provided by SVNKit. I cannot imagine what would
> cause it. Are you sure the Apache repository did not just get tied
> up? We have certainly experienced stuff like this with our Subclipse
> repository at tigris.
Yes, I'm sure. I can at the same time access it from other computer
running Windows and TortoiseSVN.
> 2. Synchronization freezes at 5-10% (about 3-4 projects synchronized)
> and after about 2 minutes my Eclipse just closes. No errors or so.
> I've tried checking out projects on http: but still no joy. Svn up
> work without any problems. This happens only on my Linux (open SUSE
> 10.2), on Windows XP I couldn't reproduce this problem. My
> 1. Subclipse 1.1.10 (with SVNkit)
> 2. Eclipse 3.2.1
> 3. Java 1.5.0_10
> I would appreciate any hints, maybe some tips how track this
> problem. Is
> there any log file for Subclipse?
> svnkit has some information on setting up logging on their home page.
Thanks for the info. Eclipse quits because of
java.lang.OutOfMemoryError: Java heap space. I'll try to dig deeper into
the problem and speak with svnkit folks.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed Feb 7 18:49:21 2007