Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-team-dev] Team Logical Model Integration for Git


Dariusz,

It's been a long time since I've looked at this code but you shopuldn't need to implement the full logical model support. I would suggest you have a look at the org.eclipse.team.internal.ui.synchronize.ChangeSetModelProvider class and see if you can make use of that. If you run into problems, the best way too find out how to proceed would be to look at how the CVS logical model support uses the class. Sorry I can't provide anything more in-dpeth than that but hopefully that is enough to get youy started.

Michael


From: Dariusz Luksza <dariusz.luksza@xxxxxxxxx>
To: Generic team support framework <platform-team-dev@xxxxxxxxxxx>
Date: 07/20/2010 07:29 PM
Subject: [platform-team-dev] Team Logical Model Integration for Git
Sent by: platform-team-dev-bounces@xxxxxxxxxxx





Hi there,

I'm this year Google Summer of Code student, my project is to improve
Eclipse's integration with Git by adding support for Synchronize view.

In current project state we can synchronize with remote branch and see
incoming, outgoing and conflicting changes. I have implemented own
subclasses of:
* SubscriberParticipant
* ResourceTreeVariant
* ResourceVariantTreeSubscriber
* SyncInfo
and provide implementation for interfaces:
* IResourceVariant
* IResourceComparator

Current solution works quite well. But there is a small issue. Git
tracks whole repository state, not a state of single file in
repository. Therefore in Synchronization view should appear list of
commits that doesn't exist in one of selected branch/tag. Then
particular commit should contains set of changes that are associated
with if. As far as I understood Team Logical Model terminology this
can be achieved by implementing proper ChangeSet.

When I was searching for any advice in Google I found this help
page[1] and especial this chapter[2] seems to be very important in
case of my problems. I even try to implement it using top-bottom
approach but I fail on some level. To be honest I don't really get
this documentation, I can't distinguish what are the pre-requirements
for having ChangeSet support, does I really need to implement all
points in roadmap?

Now I think that I desperately need some help and hints how migrate
current synchronization support on Logical Model synchronization?
Where should I begin?
What classes should be extended, what interfaces implemented and what
extension points used?
How Logical Model Integration fits for distributed version control
system such as Git is?

Thanks in advance for any help.
[1]
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/team_model.htm
[2]
http://help.eclipse.org/helios/topic/org.eclipse.platform.doc.isv/guide/team_model_repo.htm#TeamContent
--
Best regards

GSM: +48 695 192 160
Blog:
http://luksza.org
LinkedIn:
http://www.linkedin.com/in/dariuszluksza
_______________________________________________
platform-team-dev mailing list
platform-team-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-team-dev



Back to the top