David Cok <cok@frontiernet.net> wrote on 11/13/2006 03:21:25 PM:
> 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.
Please file an issue.
> - 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.
The Subversion API does not. JavaSVN added a special one that does, and
we do use it. The only way it would work with JavaHL would be if you
checked out a common parent folder using another client, and then imported
the projects into Subclipse. We would then have to detect this, which can
be hard given that the common parent is not part of the workspace. Anyway,
we do not bother to try to detect this scenario since you can only set it
up manually.
Our hope is to enhance the Subversion API to support this natively, even
if there is no common parent.
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:30:42 2006