Hi Eugene,
So far we only support outgoing changesets. Supporting incoming
changesets is possible, but it is a considerable amount of work. In
theory it is simple. Run an svn log command on each file to get the
latest history then group them by version number.
The branch you mentioned was intended only for changeset support. At
some point we will probably have to create a branch for the 3.2 stuff,
as changesets are not API compatible between 3.1 and 3.2, which means
maintaining another version of subclipse. Yay.
If you are going to be creating patches, it would be easiest to create
them against the trunk.
Adding a page to the common history view is fairly trivial. I created a
history page for Confluence a while ago if you are interested. However,
Team have added new API for versions (FileHistoryProvider, FileHistory
and IFileRevision), so it is possible they are planning on pushing some
of the CVS history page down into team (although i haven't seen any bugs
to confirm this). Also, if we implement this interface we should get
live annotate for free.
Cheers,
Brock
Eugene Kuleshov wrote:
> Hi,
>
> It looks like there is an Eclipse 3.2 branch has been created in
> Subclipse repository and there is already some work done on active
> change set support. Is it only for outgoing change sets? How about
> grouping incoming changes by revisions?
>
> I also would like to look at support for common History view
> introduced in Eclipse 3.2. Is this branch would be the right place to
> work on such patches?
>
> Thanks
>
> Eugene
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Sun May 21 09:06:08 2006