news <news@sea.gmane.org> wrote on 01/10/2006 06:46:08 AM:
> I recently changed my computer and just copied over the entire
> Subversion repository onto the new one. It seems to work just fine.
> I also have Eclipse and Subclipse installed on the new system, and I
> have copied over my working copy. Now I have some changes there that
> are not checked in yet. When I tried to check them in on the new
> machine, I got the problem that JavaHL is not installed. Indeed, I need
> it because I am using the file:/// protocol. Instead of getting through
> all the pain of recompiling Subversion with javahl on the new machine,
> as I did on the old one, I thought it would be easier to just invoke an
> svnserve -d daemon, and access my repo over svn://. This seems to work,
> I tried it with a second project that was up-to-date. I had to delete
> my WC and check it back out, though.
>
> Now for the problem: my main project has uncommited changes, so I can’t
> just delete the WC and check it back out. What is the best way to go
> now? Can I disconnect a project and reconnect it to another gateway to
> the same repo?
>
> And would there be any disadvantage that I use svn:// now over file:///?
I think that moving to svn:// is a good idea.
Subclipse has included support for svn switch --relocate since version
0.9.100. Just go to the repositories view, right click on your file://
repository and take the Relocate option. This will let you enter the new
svn:// URL and will also relocate any working copies in your workspace
that were using the file:// URL.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Tue Jan 10 15:45:58 2006