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

Why does trying to connect to an existing repository module do nothing?

From: Johnson, Graham <gjohnson_at_alpineaccess.com>
Date: 2004-02-02 22:57:41 CET

I asked this question several months ago, but didn't get a response. I
tried this again with the latest M6 build from McClain, and it still
does not work. I won't repeat all the details of the problem (see
http://subclipse.tigris.org/servlets/ReadMsg?list=users&msgNo=104), but
here's the gist of it:

I am trying to connect my Eclipse project to an existing repository.
When I try to share my project, I get as far as the dialog "Module
'[module name]' already exists remotely. Would you like to Synchronize
your local project with the existing remote module?". When I click
"Yes", the dialog closes immediately with nothing appearing to happen.
The project is still not shared, there is no error in the error log, and
the only output in the SVN Console is what was output when it detected
that the module "already exists remotely".

I suspect this happens because a large block of
org.tigris.subversion.subclipse.ui.wizards.sharing.SharingWizard is
commented out (presumably the code that would do something when I click
"Yes" in the dialog mentioned above). I am not set up to develop
Eclipse plug-ins, so I can't easily test this myself.

Is anyone able to successfully use the "Synchronize your local project
with the existing remote module" functionality?

Graham Johnson
Java Software Engineer
Alpine Access, Golden, CO
Received on Tue Feb 3 08:57:41 2004

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.