Migrating svn repository from eclipse 3.2 to 3.3

[mkearney]

I ran into some flak migrating my windows svn repository from eclipse 3.2 to
3.3.
I got lucky. Some magic happened after many error messages and apparent
failures
and now it works, but I can't tell why I finally succeeded.

These are my notes beginning from a point where nothing seems to work to
when
the magic happened. I also suggest some wording changes to your help docs.

----------

I am migrating from eclipse 3.2 to Europa eclipse 3.3. I have a svn
repository
that was accessible via subclipse under 3.2. I can't seem to figure out how
to
get it working under 3.3. It seems to me that it should be just a matter of
telling subclipse where the repository is and things should work from there.

1. I have confirmed that the repository has not been compromised in the
eclipse upgrade.
From the command line:

svn info svn://localhost
Path: localhost
URL: svn://localhost
Repository Root: svn://localhost
Repository UUID: 1fc2b68e-6379-cb42-89b4-c2a30ace8b31
Revision: 44
Node Kind: directory
Last Changed Author: mkearney
Last Changed Rev: 44
Last Changed Date: 2007-07-10 14:21:15 -0400 (Tue, 10 Jul 2007)

2. I looked into the subclipse help documentation. The "Getting Started"
section
has a heading, "Creating a New Repository Location". Now I am going to
quibble about
the English here, because I found it confusing, and others might as well.
The Overview sentence says:

"Before you can begin working with a SVN repository, you must define that
repository location to your Eclipse IDE."

(I presume "your Eclipse IDE" means Subclipse?)

As I understand and have experienced, Subclipse provides a great layer of
functionality
that enables most subversion functionality from within Eclipse, at least
most if not all
of what is possible through the Subversion API.

However, I believe I understand from subclipse that a user cannot "Create a
New Repository".
Nor can one "Create a New Repository Location". Both of those functions have
to be
performed at the command level when a user or admin is setting up svn.
Correct me
if I am wrong.

What the user can do is to tell subclipse which svn repository repositories
it can
access. The user then opens the SVN browsing perspective and clicks on the
svn+
icon to invoke the dialog for adding a svn repository to subclipse.

So if I have this correct, then I suggest that the heading should be:
"Adding a Repository to Subclipse" or just "Adding a Respository"

hmmm , I just discovered that there are links to this page titled, "adding
a New Repository Location". See the Checking Out a Project" page. I'd still
say drop both of "new", and "location". THe repository need not be "new".
"location" is redundant.

And that sentence should be something like:
"You must add a repository to subclipse before you can access it."

Am I correct in all this?

3. Assuming I am correct. I can't figure out what URL to give subclipse.
I have tried:
svn://localhost

I am getting error pops complaining about the url. Most of the info
contained
in the popups is showing up on the subclipse console as shown below

RA layer request failed
svn: PROPFIND request failed on '/localhost'
svn: PROPFIND of '/localhost': Could not resolve hostname `svn': No such
host is known. (https://svn)

RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': Server certificate verification failed: certificate
has expired, certificate issued for a different hostname, issuer is not
trusted (https://oak)

RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://oak)

RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (https://oak)

RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://localhost)

RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://127.0.0.1)


Oh joy... I tried
svn://localhost
again. Got more noise like above, and just hit return again

<magic occurred here>

and the thing loaded without further error.
Well something loaded.

I was able to check out a project.......
And modify and submit a file

egad...


Detail:
OS: Windows-xp service pack 2

---------------

[Mark Phippard]

Post by mkearney
I ran into some flak migrating my windows svn repository from eclipse 3.2 to
3.3.
I got lucky. Some magic happened after many error messages and apparent
failures
and now it works, but I can't tell why I finally succeeded.

Let's get language clear here. Your repository and Eclipse are not
directly related to each other. Perhaps the repository lives on the
same physical PC but it is still not something you create from Eclipse
or is in anyway impacted by an upgrade or change in Eclipse.

Post by mkearney
I am migrating from eclipse 3.2 to Europa eclipse 3.3. I have a svn
repository
that was accessible via subclipse under 3.2. I can't seem to figure out how
to
get it working under 3.3. It seems to me that it should be just a matter of
telling subclipse where the repository is and things should work from there.

Yes, exactly. Following up to previous comments I made. All you do
in Eclipse is point Subclipse to the URL of a repository.

Post by mkearney
However, I believe I understand from subclipse that a user cannot "Create a
New Repository".
Nor can one "Create a New Repository Location". Both of those functions have
to be
performed at the command level when a user or admin is setting up svn.
Correct me
if I am wrong.

Creating a Location is the terminology we use in Subclipse to mean
tell us about a Repository.

Post by mkearney
3. Assuming I am correct. I can't figure out what URL to give subclipse.
svn://localhost
I am getting error pops complaining about the url. Most of the info
contained
in the popups is showing up on the subclipse console as shown below
RA layer request failed
svn: PROPFIND request failed on '/localhost'
svn: PROPFIND of '/localhost': Could not resolve hostname `svn': No such
host is known. (https://svn)
RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': Server certificate verification failed: certificate
has expired, certificate issued for a different hostname, issuer is not
trusted (https://oak)
RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://oak)
RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (https://oak)
RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://localhost)
RA layer request failed
svn: PROPFIND request failed on '/'
svn: PROPFIND of '/': 302 Found (http://127.0.0.1)

There is no way that Subclipse or Subversion API would give errors
like this unless there was a reason. You must have been entering
URL's like http://something. Clearly your URL is svn://localhost as
that is what you entered to svn info command and that is the exact
command we run from Subclipse.

Maybe you have configured proxy information somewhere and that is
producing these error messages. I have never worked with a proxy so
do not know. The command line and Subclipse use the same
configuration area though, so I cannot see one getting the errors and
the other not.

[mkearney]

Two observations:

1. As soon as I type "s", or any other character, I get the error message,
"The repository path must be a valid URL Invalid svn url:s" , in the "Add
SVN Repository" popup. I see how I got confused.IMO, It would be better if
URL correctness was checked only after the URL is fully entered. I don't
know if Subclipse controls that particular widget or not. If not, then you
can only warn about it.

2. The Subclipse Documentation and tools uses both "Create a new Repository
Location" and "Add a new repository" to mean tell Subclipse about a
Repository. I suggest you chose one or the other. As I said, " I would
prefer, "Add a Repository". I found that the prominence of the "Create a new
Repository Location" lead me in the wrong direction for a while. Ultimately,
you decide.

regards,
-m