"Elijah Baley" <e_baley@hotmail.com> wrote on 11/15/2005 09:38:11 AM:
> Architecture: Windows 2000 and/or XP-SP2, Eclipse 3.1.1, JDK 1.5.0_05,
> latest subclipse plugin
>
> Scenario:
> - checkout the files using TortoiseSVN to the local disk
> - start Eclipse
> - define a workspace at the parent (!) folder of the project - e.g.,
if
> project root is at "D:\Projects\foo\bar" then workspace is defined at
> "D:\Projects\foo"
> - define a project having the same (!) name as project's folder
(e.g.,
> "bar") - this causes the Eclipse to auto-detect its presence and start
the
> SVN synchronization
>
> For some reason, on some (but not all !) hosts the CPU hangs at 99% at
this
> stage forever (I let it do so for more than 3 days). The fix is to
choose
> JavaSVN instead of JavaHL and everything seems to work OK.
>
> AFAIK there are not noticeable differences between the hosts where
JavaHL
> works and those that do not - some are 2000, some are XP but it seems
like
> a 50-50 chance for it to work regardless of Windows version (2000 or XP)
>
> Can anyone offer an explanation/fix (while it does not seem urgent since
the
> JavaSVN works for the time being, it might be worth exploring - at least
for
> a future release).
I do not know what the problem is, but I would not do the technique you
are doing. What I would recommend is creating a workspace in a different
location and then use File -> Import -> Existing Projects into Workspace
in Eclipse. Then point it at the TortoiseSVN checkout. This will then
point Eclipse at the folder without also putting the workspace stuff in
there.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Nov 16 01:46:39 2005