Community
Participate
Working Groups
I want to separate the "ui" and the "core" functionality in my Mylyn connector. My "RepositoryConnector" is in my "core" plugin which depends only on "org.eclipse.mylyn.tasks.core". I need to find a task or a taskData for its id in my "RepositoryConnector", but there are no APIs in "org.eclipse.mylyn.tasks.core" for this. I don't want to have dependency on "org.eclipse.mylyn.tasks.ui" in my "core" plugin. A solution may be to create an activator for "org.eclipse.mylyn.tasks.core" and to initialize the data managers (TaskDataManager ...) there. Best regards Beyhan
Hi, any update on this? Kind regards, Jan
Sorry for the slow response. Connector cores are intentionally designed as state-less singletons and are not expected to hold on to or access the state of a particular IRepositoryModel instance directly. I understand that this can be limiting sometimes. Can you describe why it is necessary for your connector core to obtain instances to tasks not already provided when methods on the connector core are invoked? It would help us to understand the use cases better and potentially reconsider this design in the future.
I can't remember anymore the use case. Since almost two years I'm no more in this project. I think our tasks had dependencies between them and in our *.core bundle wasn't possible to find out whether the dependencies of a task are already loaded or have to be loaded. I hope this can help you.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
