[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [Subclipse-users] Problem with atomic commits

From: Schechter, Michael <MSchechter_at_national.aaa.com>
Date: Fri, 1 Aug 2008 14:27:45 -0400

Mark,

I noticed recently that you were working on a 1.4.3 release of Subclipse. Is issue 783 related to my question?

If so, that's great news, as this was the only sticking point in our entire Mylyn/Subversion/Bugzilla workflow. Do you have any idea yet when you plan to release v1.4.3?

Thanks!

Michael Schechter
mschechter_at_national.aaa.com
RESPONSESupport_at_national.aaa.com

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Wednesday, July 23, 2008 10:15 AM
To: users_at_subclipse.tigris.org
Subject: Re: [Subclipse-users] Problem with atomic commits

On Wed, Jul 23, 2008 at 8:46 AM, Schechter, Michael <MSchechter_at_national.aaa.com> wrote:

> It is most confusing to me because the behavior of the plug-in (if I
> am understanding your explanation correctly) is based on how I
> configure my workspace (projects within vs. projects external). I
> would strongly recommend that this be re-examined as either a new feature, an enhancement to the existing atomic functionality, or a bug.

The issue is that at the API level Subversion does not support this, at least in the normal case. Meaning, when all of your projects are checked out and live in your Eclipse workspace folder, they are all separate working copies. There is no common parent to them. In this scenario, Subversion does not all you to commit from all these working copies in a single transaction. We work around this by grouping the commits by parent directory and repository and then "tricking"
Subversion into thinking they are all part of a common working copy.

In your case, they actually do (I think) all live in a single common working copy. It is just that from the Eclipse view in our code there is no simple way for us to know this. We would have to evaluate all the files in your commit and go do all this checking to see if they are all rooted in a working copy. We have added some fairly complex logic already, but not complex enough to handle your scenario.

> In addition, I would like to request that the documentation be updated
> to reflect both the current preferences interface and this behavior.

None of the documentation has been updated since our 1.0 release. We are an open source project and rely on the contribution of volunteers.
 Patches are welcome. See this page for information on getting started with development for Subclipse.

http://subclipse.tigris.org/dev/

--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-01 20:28:10 CEST

This is an archived mail posted to the Subclipse Users mailing list.