RE: [Subclipse-users] Problem with atomic commits

Mark,

All projects are under a common root directory under my trunk. All projects exist at various levels within that structure - we have two top-level parents, and one has additional directory structure while the other does not (all its projects are at the same level).

It looks something like this:

{repo}/svn/{svn_project}/trunk
        - {code root}
                - {tree root 1}
                        - {eclipse_project_1}
                        - {eclipse_project_2}
                        - {eclipse_project_3}
                - {tree root 2}
                        - {structure 1}
                                - {eclipse_project_1}
                        - {structure 2}
                                - {substructure 1}
                                        - {eclipse_project_2}
                                        - {eclipse_project_3}

If I am reading your explanation correctly, this implies that I should get a single commit, as I imported all projects from {code root}.

In case it matters, I was using Team Synchronizing in 'flat' mode (just files displayed). Could how I have defined the repository in the Eclipse repository explorer have had an effect?

Thanks!

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

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Tuesday, July 22, 2008 3:53 PM
To: users_at_subclipse.tigris.org
Subject: 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