Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 322946

Summary:	[changeset] implement ActiveChangeSetManager and ActiveChangeSet
Product:	[Technology] EGit	Reporter:	Chris Aniszczyk <caniszczyk>
Component:	UI	Assignee:	Project Inbox <egit.ui-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	dariusz.luksza, steffen.pingel
Version:	0.9.0
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Chris Aniszczyk

2010-08-17 15:36:50 EDT

There's some missing pieces in our changeset implementation in order to integrate with Mylyn.

Comment 1 Chris Aniszczyk

2010-08-17 15:38:24 EDT

We may need a SubscriberChangeSetManager also.

Comment 2 Chris Aniszczyk

2010-08-17 16:04:15 EDT

I put some code on GitHub that we can start hacking Dariusz.

I'm going to flesh out some of the task integration I've been thinking about.

http://github.com/caniszczyk/mylyn-git

Comment 3 Steffen Pingel

2010-08-19 21:34:13 EDT

You could also consider implementing AbstractContextChangeSetManager if you want to avoid dependencies on ActiveChangeSet.

Comment 4 Chris Aniszczyk

2010-08-20 11:02:34 EDT

(In reply to comment #3)
> You could also consider implementing AbstractContextChangeSetManager if you
> want to avoid dependencies on ActiveChangeSet.

Do you have any examples I can look at or point me in the right direction of what needs to be implemented in AbstractContextChangeSetManager?

Comment 5 Steffen Pingel

2010-08-20 18:43:23 EDT

I thought there was another implementation of AbstractContextChangeSetManager but it turns out that I was wrong. Looks like ActiveChangeSetManager provides the persistence and management for change sets and is what CVS, Subclipse and Subversive use. If it's feasible it's probably the best way to go with that otherwise EGit would need to re-implement a significant portion of the change set management.