I plan on getting started working on the Subversion 1.2 features like
I have done some preliminary testing and I think it is going to be
difficult, if not impossible, to build Subclipse so that it can work with
a JavaHL from 1.1 and/or 1.2. If it were just the locking, I think it
would be pretty easy to just hide those options or handle the errors, but
the changes seem more pervasive than that.
1) The Notification framework appears to have changes in it. When I do
actions like update or commit they work but I do not get the detailed
console output I normally do.
2) API changes we need. I suspect that svn cat will work even if we do
not make changes, but otherwise there is a new API signature we need to
use. Also, I want to enhance svn log to support the new features to just
retrieve a specific number of revisions.
3) If I just drop in the JavaHL binary but leave the old JAR, it does not
work. If I drop them both in it works. However, we ship the JAR so once
we ship the 1.2 JAR I suspect it would fail if they had the 1.1 binaries.
4) Dependency changes. We try to load the JavaHL dependencies and the
names of at least one of them have changed.
With all that in mind, I am thinking we may just have to move on to 1.2
and have our next release require it.
Thoughts or comments?
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Wed Apr 13 01:43:23 2005