Marc Sherman <msherman@projectile.ca> wrote on 12/01/2005 01:34:05 PM:
> Mark Phippard wrote:
> >
> > Basically it just means if you want to use the JavaHL or CLI adapter,
and
> > you are not on Windows, you need to support a binary from Subversion
1.3.0
> > RC4.
>
> Are you still recommending JavaSVN over JavaHL with this new release, or
> does JavaHL now include all the new APIs you need for the
> high-performance options JavaSVN was giving you in the last few revs?
In theory, JavaHL has the improved status output that lets Syncrhonize run
faster. Just today, I discovered it is not working via DAV and I put a
workaround into Subclipse. It does work fine via svn://
JavaSVN has some other niceties still that JavaHL does not:
1) A huge one is that with JavaSVN, if you do a commit that involves
several Eclipse projects from the same repository, then JavaSVN will
commit them all in one atomic commit, as opposed to one per project.
2) The new Resource History view does page at a time loading. With
JavaHL, when you page past the beginning of a branch, you will get an
exception. JavaSVN does not have this problem because it handles peg
revisions differently by default in svn log.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Fri Dec 2 06:14:09 2005