[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mylar-dev] Extraction of RepositoryTaskData from AbstractRepositoryTask
|
Currently, AbstractRepositoryTask holds onto an instance of
RepositoryTaskData which has resulted in a few problems. In many cases,
instances of AbstractRepositoryTask make use of the RepositoryTaskData
to determine values such as the task summary. If the offline
RepositoryTaskData becomes unavailable, the task may no longer be able
to determine the task summary. This can happen for a number of other
fields and affects most connectors.
Additionally, by pulling RepositoryTaskData out of
AbstractRepositoryTask, followed by completion of the proposed changes
to offline persistence
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389) we will
effectively achieve lazy loading of RepositoryTaskData and consume less
memory.
Finally, by forcing retrieval of RepositoryTaskData from the
TaskDataManager, we can minimize the chances of data inconsistencies.
For more information on these changes you can follow along here:
181038: [api] Pull RepositoryTaskData from AbstractRepositoryTask and
fix synch of data
https://bugs.eclipse.org/bugs/show_bug.cgi?id=181038
Also note that the Mylar Porting Guide is being maintained to help ease
adoption of such changes.
http://wiki.eclipse.org/index.php/Mylar_Porting_Guide
-Rob
