On Wed, 26 Oct 2005, Alexander Kitaev wrote:
> > JavaSVN might not always be available, but more importantly,
> > it also might not always work. Examples: no ra_local, WC
> > format changes it doesn't understand (JavaSVN 0.9.2 against a
> > SVN 1.3 WC will produce this), etc.
> Just to clarify that. If I do not miss anything, current stable version of
> JavaSVN (one included into 0.9.36) will work well with Subversion 1.3. wc
> format (including dot_net hack). It will not use new "repos" entry property,
> but will not fail. I think that at the time Subclipse for 1.3 is released
> there will be a new version of JavaSVN with full support for 1.3 features.
Alexander, I was referring specifically to:
...which has been confirmed via the JavaSVN source not to work with that
previous release. I have not checked your dev branches to see if this
late-breaking change has been subsequently handled (it's been less than
a week since Dan Berlin made this change Subversion's own source tree to
drastically reduce the size of gcc's working copies).
p.s. I'm really hesitant about eating off of a development branch. At a
minimum, the source for the JavaSVN JAR included in svnClientAdapter (and
thus Subclipse) should be easily reproducable. Would it be possible to get
a beta or alpha tag for the version of JavaSVN we include?
Received on Thu Oct 27 07:29:06 2005