David Cok <cok@frontiernet.net> wrote on 11/13/2006 01:32:52 PM:
> Anyone else run into this annoyance:
>
> The Subversion UI in Eclipse allows one to commit a whole project at
> once. However, when there are multiple related projects within one
> WorkingSet, it would be convenient to be able to execute a Subversion
> action on all the projects by right-clicking on the WorkingSet in the
> Package Explorer. Currently no Subversion actions are enabled on
> WorkingSets.
>
> If they were, the natural action would be to issue the requested command
on
> each project in the WorkingSet in turn. In my case the WorkingSet
> could correspond to a Subversion action at one level higher in the
> directory tree - which would mean that just one commit (say) would be
> issued rather than one for each subdirectory.
It is true that there are no options hungs off working sets, and in some
cases it could be convenient to have such options. However, it is not
correct to think that having such options would allow you to do an atomic
commit across several projects. That is a Subversion API issue. We
already support doing this if you select multiple projects and use the
Commit option, provided that you are using JavaSVN as your client
interface. The native Subversion libraries do not support atomic commits
unless all of the projects are beneath a common working copy folder, and
Subclipse doesn't support it even in that scenario as there is no
realistic way to check that.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Nov 13 19:43:03 2006