Thanks for the comment, Mark.
- In my working style, at least, it would be handy to have the actions
be available on the WorkingSet, even if the result was individual
commits/updates on each of the underlying projects.
- In this particular case, the projects all do map to parts of a single
SVN working copy. In fact, Eclipse's Package Explorer indicates the
subdirectory each one comes from and the project properties indicate the
whole Subversion URL for the project root. So it seems one could tell
that the projects were all part of one working copy. One cannot
necessarily translate that into a single commit/update at a higher level
in the directory tree (one would have to be sure that the projects in
the working set constituted all of the working copy). However, it does
seemm in principle that one could pass all of the related directories to
a single commit/update, if the API between Subclipse and Subversion
allowed that.
- David
Mark Phippard wrote:
>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 21:21:45 2006