http://subversion.tigris.org/issues/show_bug.cgi?id=2381
------- Additional comments from dlr tigris.org Fri Mar 30
13:18:48 -0700 2007 -------
Mark Phippard's initial report from issue 2724 (for easy
access):
The Eclipse environment, probably most IDE's, create an
environment where
projects are checked out into a common folder where the
parent folder is not a
WC. So even though all of these projects are from the same
repository and might
even have a common parent, they are essentially a series of
disconnected
"island" working copies. The problem with this is
that you can then not commit
changes in multiple projects as a single atomic commit
operation.
Expected behavior:
If I commit files, listing their paths, and they all live in
the same
repository, I would expect the commit to succeed and do it
one transaction.
Actual behavior:
Subversion errors out if you try to do this. As a
workaround, Subclipse has to
break this up into multiple commits. Users feel like they
are losing a key
Subversion feature.
Suggested change:
The JavaSVN/SVNKit library added support for this. In their
case, we just have
to give them all the paths, and they break it up into one
commit per repository.
I would be happy doing this break up in Subclipse, if I
could just get the
single commit to work when they are all in the same
repository.
------------------------------------------------------------
---------
To unsubscribe, e-mail: issues-unsubscribe subversion.tigris.org
For additional commands, e-mail: issues-help subversion.tigris.org
|