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

Re: Commits in different projects results in separate commits

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-09-06 03:00:55 CEST

> If I make changes across multiple (and dependent) projects and commit I
require that the whole
> commit to be a single “atomic” commit, however subclipse doesn’t a
separate commit for each
> project rather than one big commit.

The good news is that pretty much everybody would like to see this feature.
The bad news, is that it is pretty hard to do, although I think someone was
looking at it a while ago. First off, I do not think it will ever be
possible to do it using what I would call a "normal" scenario where you use
Subclipse to check out your projects. In that scenario, each project is a
unique working copy and the Subversion library does not support it. In
order to get this feature, you have to do your checkout using some other
Subversion client, so that you have a single working copy with all of your
projects in it. You can then use the Eclipse Import option to import the
project into the workspace. In Eclipse 3.1, Subclipse will even
automatically connect up to the project, In 3.0, you have to follow it up
with a Team -> Share. This is documented in the online help of the latest

Anyway, in this latter scenario, it should be possible to somehow support
this feature. For now, you can do your commits using another client, which
is what I do when I need to do it.


Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
Received on Tue Sep 6 11:00:55 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.