RE: [mylyn-integrators] Mylyn 2.0 API status

["Mik Kersten" <beatmik@xxxxxxx>]

The API clean-up is now complete.  There were no changes in functionality,
only naming improvements and moves of internals to mylyn.internal..
packages.  In doing so we have ensured that none of the connectors use any
internals so our expectation is that other connectors will not need to do so
either.  All of the Pending Changes in the Porting Guide have been applied
and the porting guide has been updated.  If anyone has any difficulty in
porting that is not addressed by doing a "Find" of the corresponding type or
method name in the Porting Guide please do not hesitate in firing off an
email to mylyn-integragors so that we can clarify.  Also, as always feel
free to amend or correct the document: 

http://wiki.eclipse.org/index.php/Mylar_Porting_Guide

Mik

> -----Original Message-----
> From: mylyn-integrators-bounces@xxxxxxxxxxx [mailto:mylyn-integrators-
> bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
> Sent: Thursday, June 21, 2007 9:35 AM
> To: mylyn-integrators@xxxxxxxxxxx
> Subject: [mylyn-integrators] Mylyn 2.0 API status
> 
> The API improvements for 2.0 are complete.  Our driving goal for the
> API
> changes was to make connectors much easier to build by better
> insulating
> them from the implementation details of the Tasks API.  We also wanted
> to
> stabilize the APIs to the point where we could commit to backwards
> compatibility (i.e. 2.1, 2.2...) throughout the majority of the
> upcoming 3.0
> release cycle.
> 
> The only significant change this week was to replace the messy legacy
> task
> externalizer architecture with element factories.  The
> repositories/taskListFactories extension point uses the very simple
> AbstractTaskListFactory which connectors now override to provide
> specific
> attributes on elements and to instantiate them rather than having to
> handle
> the details of the XML externalization.  We will be updating the
> porting
> guide this and next week, and for now the Trac connector provides a
> concise
> example of how a factory should work.
> 
> Please note that we will still be doing the following clean-up, which
> may
> cause some class or method names to change:
> * Review to ensure no internals are in public packages.
> * Ensure no connectors or bridges use internals.
> * Review and provide Javadocs for every public type.
> 
> Mik
> 
> --
> Mik Kersten
> Project Lead, http://eclipse.org/mylyn
> 
> 
> 
> _______________________________________________
> mylyn-integrators mailing list
> mylyn-integrators@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-integrators