Hello,
Recently I noticed, that when commiting files from different Eclipse
projects that are checked out from the same repository (and actualy share a
common wc root - Eclipse workspace) - Subclipse divides changes into
separate commits, which virtually removes all advantages if subversion
transaction feature - instead of one atomic change user gets several ones
(up to the number of projects), which is especially annoying when small
change were applied to let say 100 projects - one will get 100 transactions
instead of one.
What I would like to suggest is to change Subclipse commit behaviour the
following way:
- Try to commit all modified files in all projects. JavaHL, as well as
JavaSVN will check whether files belong to the same repository and will
throw an exception if files are from the different repositories. However
commit will proceed normally when files are from the same repository and may
be committed with the single commit operation.
- If exception was caught on the first attempt (and there is a
distinguishing message in the exception, so it is possible to separate auth
or connection failure from the multiple repositories commit attempt
failure), use the old way.
Other possibility is to run "status" command on the workspace root (or
project parent directory(ies)) to make sure that files to be comitted
belongs to the same working copy.
Alexander Kitaev.
Received on Tue Mar 15 06:33:07 2005