What does my subclass of ContextActiveChangeSetManager need to do in order to fulfill the contract in the contextChangeSetManager extension point and implement team support for Mylyn for a source control provider? Is that what I need to implement if there is no implementation of ActiveChangeSetManager available for my provider?
Because I'd like to get the benefits of Mylyn's team support even though our provider, Perforce, doesn't yet support Mylyn in their P4WSAD Eclipse plugin. We have access to Perforce's Java API, so I suspect that I can put this support together myself. The Mylyn Integrator docs mention both the "activeChangeSetProvider" and the "contextChangeSetManager" extension points for source control integration. The first one appears to require a source-control-system-specific implementation of ActiveChangeSetManager, which P4WSAD doesn't supply. The second one suggests that it doesn't, and offers ContextActiveChangeSetManager as an example of how to implement it, and maybe if I look at that class and its superclasses long enough, I'll understand what I need to do, but it sure isn't evident. Hence my opening question. Incidentally, I've written my own connector for our in-house bug tracking system. I don't have to write special support in that connector for source control, right? Larry Edelstein Senior Member of Technical Staff Salesforce.com [email protected]_______________________________________________ mylyn-integrators mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
