[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mylyn-versions-dev] SCMArtifact and SCMArtifactInfo
|
Here is a concrete example how the current API is intended to be used,
assuming that IResoruce is a known resource:
ScmConnector connector = ScmCore.getConnector(resource);
if (connector == null) {
return;
}
Artifact artifact = connector.getArtifact(resource);
IFileRevision left = artifact.getFileRevision(previousRevision, new
NullProgressMonitor());
IFileRevision right = artifact.getFileRevision(revision, new
NullProgressMonitor());
ScmUi.openCompareEditor(getPage().getSite().getPage(), left, right);
Steffen
On Wed, Jan 19, 2011 at 4:44 PM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
> The rationale behind ScmArtifactInfo is that it's lightweight
> reference to a particular revision in an SCM repository, so maybe
> ScmArtifactRevision would be more suitable name. It's not coupled a
> particular SCM connector and does not implement significant behaviour
> to support persistence without requiring connector class loading. I
> was thinking that the builds framework would use ScmArtifactInfo
> objects, e.g. for UI presentation, and only create the corresponding
> ScmArtifact object if the artifact is actually accessed. Does that
> make sense?
>
> Steffen
>
>
> On Wed, Jan 19, 2011 at 4:34 AM, alvaro sanchez <alvsan09@xxxxxxxxx> wrote:
>> Hello,
>> One more question,
>> I am trying to figure out if we need these two elements or shall they be merged.
>>
>> Not sure on the added value to have them separated.
>>
>> /Alvaro
>> _______________________________________________
>> mylyn-versions-dev mailing list
>> mylyn-versions-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/mylyn-versions-dev
>>
>
>
>
> --
> Steffen Pingel
> Committer, http://eclipse.org/mylyn
> Senior Developer, http://tasktop.com
>
--
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com