Re: [Subclipse-users] Problem with atomic commits

On Tue, Jul 22, 2008 at 3:45 PM, Schechter, Michael
<MSchechter_at_national.aaa.com> wrote:
> I have just started using Eclipse Ganymede and Subclipse 1.4.1 (with JavaHL
> 1.5). We chose to continue using Subclipse specifically because the
> cross-project commit issue (your issue 527) had been addressed.
>
> For some reason, when I did a cross-project commit from the Team
> Synchronizing view, I got one commit per project. This is not what I
> expected, nor what the documentation led me to believe (the help documents
> are out of date, by the way).

The commits are still grouped by the parent folder of the projects in
your workspace. So if they are not all in the same parent it cannot
group them. As an example, I have a checkout of trunk, and it has two
folders, features and plugins. I then import all the Eclipse projects
from those folders into my workspace. When I commit, I get two
commits. One for everything under plugins and one for everything
under features.

In a "normal" Eclipse workspace, the workspace folder would be the
parent and they would all go in a single commit.

-- 
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