On 7/16/07, mkearney <ma.kearney@verizon.net> wrote:
>
> 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.
> 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.
> 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.
> 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)
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.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Jul 16 19:08:00 2007