Kristian Duske <email@example.com> wrote on 11/11/2006 01:56:13 PM:
> I then imported my projects using the Eclipse import wizard from my
> old workplace. Upon committing, the error showed up again, so I
> checked the Subclipse configuration and noticed that it was
> complaining about missing JavaHL binaries. I switched to JavaSVN, but
> the error did not go away. I guess Subclipse was using JavaSVN as a
> fallback anyway.
I bet it had something to do with importing a project that had a 1.3 WC
into Subclipse. Alex was alluding to this earlier. Perhaps there are
scenarios where JavaSVN runs into a problem in converting the WC to the
1.4 format leaving it in an in-between state. Maybe Alex will see this
and test the scenario.
> I know you don't like this, but as I said my problem seems to
> resemble what Jerry described. Now I don't know much about subversion
> and it's meta information, but it seems that maybe Subclipse isn't
> updating the present .svn files for me. If you want, I can send you
> some sample .svn files to have a look at.
It is not an issue of me liking something or not. The problem is that
Jerry is confusing people, such as yourself. When a 1.4 SVN client
touches a WC it converts it to the 1.4 format silently and automatically.
That is a fact. No one, including Jerry disputes that. I am not
disagreeing with Jerry when he has said that. There are 2 areas where I
was saying Jerry was adding confusion.
1. He implies that Subclipse cannot read 1.4 formats. That is not true
at all. First off, Subclipse neither reads or writes your WC. Subclipse
executes SVN API's that are either provided by JavaHL or JavaSVN and they
read/write your WC. If you are using a 1.4.x version of JavaHL then it
has all of the same characteristics as the 1.4.x command line. Likewise,
JavaSVN, as of the 1.1.0 Beta 5 also supports the 1.4.x format. Subclipse
1.1.8 includes these versions.
2. He has said a few different things about server versions, I think some
of the more recent statements have been true but do not remember them all.
The bottom line is that the server version is not relevant. A 1.4.x
client can talk to any server 1.0.0 up to the latest. Regardless what the
server version is, the client will use the new WC format.
> If there's anything you need me to do so that we can nail this
> problem down, I'm happy to do it. It's the least I can do. I think
> you guys are providing a great service here, I wouldn't have expected
> to get so much help and friendliness. Thanks again for that.
I think that Alex might have asked you for a piece of your WC at one
point. He writes JavaSVN, so he would be the one that would need to say
what he needs or does not need.
> Hmm. I'll look into this once my projects commit fine again, but am I
> wrong in assuming that for svn+ssh, I don't even need Apache, and
> thus, I don't need APR? As I understand it, APR is only being used by
> subversion when accessing it through Apache?
Yes, that is a common mistake. Subversion uses APR for everything. Has
nothing to do with Apache. APR is just a cross platform C-library. It
happens to be used by the Apache httpd server, but it is not tied to the
server. Subversion uses APR to achieve cross platform behavior. So all
elements of Subversion use and require APR.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Nov 12 03:40:32 2006