Schenkenfelder Robert wrote on Wednesday, July 16, 2008 8:03 AM: > I can also add a new query to my repository > with the same name of the old query. Shouldn't he at least say > something to me?
That was certainly possible in 2.3. Individual connectors had to guard against it. I asked about this very issue last month. Here's what Robert said. Robert Elves wrote on Monday, June 02, 2008 5:21 PM: > To date, connectors have been handling conflicts of this nature in the > query page ui. As you point out, this is not ideal and we are > improving this for Mylyn 3.0. The framework will guard against handle > conflicts of this nature and throw the appropriate exceptions where > necessary. To follow resolution of this issue, consider adding > yourself to the cc: > > 234767: make sure handles are unique within task list > https://bugs.eclipse.org/bugs/show_bug.cgi?id=234767 Maybe check out that bug and confirm that it's fixed. I haven't used 3.0, yet, so I'm not sure how this works from the connector author's perspective. > After closing and reopening the test workbench, the synchronizing is > gone. The query was obviously saved wrong and/or non-persistent. In 2.3, I think that you needed the org.eclipse.mylyn.tasks.ui.repositories extension point, where you would identify your externalizer with the taskListFactory. That extension identified a AbstractTaskListFactory subclass, and it was used by Mylyn in persisting queries and tasks in the Task List. I believe that these APIs relied on the ability to convert a query to and from a URL. I suspect that some of this API has changed for Mylyn 3.0. -- Tom Bryan <[EMAIL PROTECTED]> Software Engineering Solutions (SES) Cisco Systems RTP, NC, USA _______________________________________________ mylyn-integrators mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/mylyn-integrators
