> Further, I went from a reasonably stable environment with 0.9.30 to
> completely unusable with 0.9.31 and had to downgrade. The JNI
> intrerface no longer worked with either my local SVN or Apache's, and
> the command line interface failed as well (it hung Eclipse, apparently
> starting ssh.exe sub-processes in a loop forever. No idea what it was
> doing ... may have been trying to collect QuickDiffs).
Subclipse 0.9.31 requires Subversion 1.2. Your problems sound like what
would happen with a 1.1 binary.
As to the issues in the email you quoted.
1 & 2) In my opinion we made a mistake in that we ever enabled the
Synchronize action before it was done. Even though we document that it is
still under development, people seem astonished that there are bugs with
it. We should have just hidden the option until it was done.
FWIW, in the 0.9.32 release, due out in about a week, a lot of progress has
been made specifically in this area. I cannot promise there will not be
any bugs, but most of the known ones, like the ones mentioned in your
email, are gone.
3) This behavior was by repeated request. Nontheless, it is a preference
under Team -> SVN whether to select or deselect unversioned files by
default. I guess the argument for the current method is that it is worse
to commit a file accidentally, but I suppose that is debatable. Anyway,
that is why we made it a preference when we changed the behavior.
4) I can't imagine why that would happen. Ideally, instead of saying our
work sucks, he would file a bug report or post a message to this list to
see if anyone else has the problem.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Mon Jul 11 11:11:33 2005