Community
Participate
Working Groups
Build Identifier: the TaskRepository class enables the presistence of user defined properties for each repository. however it's implementation is purely a regular property map. while it is suffcient for simple properties like single values strings or booleans. more complex configuration are harder to implement. a classic example would mapping tables. there are my occupations where a one to one mapping between mylyn's properties and the repo's can be specfied using a ui, like a prioraty mapping and task kind mapping or even field mapping when a user can configure which field is a prioraty and which task kind, which is due_date. i feel that perhaps a seperate configuration object should be created for this, allowing complex strucutes (like xml) to be stored and retrieved. Reproducible: Always
Thanks. This is tracked on bug 150680. *** This bug has been marked as a duplicate of bug 150680 ***