Re: [mylar-dev] enhancements in Mylar team API

[Michael Valenta <Michael_Valenta@xxxxxxxxxx>]

Eugene,

From this wiki entry, it would appear
that Mylar has API that depends on internal code from the Team component
(i.e. ActiveChangeSetManager). Is this true? If so, this is a big mistake.
If the Mylar API has internal classes in it's API, making these classes
API would end up breaking the Mylar API. 

In this particular case, even if the
class in Team were API, it should be viewed as an implementation detail
of the repository provider and not API that is usable by third party clients.
Mylar should define it's own API for change sets that repository providers
can provide custom implementations of. As a convenience, you could provide
a bridge so that users of ActiveChangeSetManager get Mylar integration
for free. However, you should not force repositories to use ActiveChangeSetManager
as they may have their own classes for managing change sets (as is mentioned
in comment 4 of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=116084).

Michael

mylar-dev-bounces@xxxxxxxxxxx wrote on 12/05/2006
01:45:20 AM:

> 
>   To anyone who interested in integrating with Mylar's Team API
> (primarily developers of plugins for version control systems), there
was 
> some enhancements been made.
> 
>   I updated correspond section on Mylar wiki at
>   
> http://wiki.eclipse.org/index.
> php/Mylar_Integrator_Reference#Integrating_Team_Providers
> 
>   regards,
>   Eugene
> 
> PS: updated plugin for Mylar integration had been already contributed
to 
> Subclipse project
> 
> 
> _______________________________________________
> mylar-dev mailing list
> mylar-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylar-dev