Community
Participate
Working Groups
BugzillaClient getTaskData did not set the Version. This results in call of the migrate for every version all the time we read the repository
Created attachment 112262 [details] mylyn/context/zip
Created attachment 112263 [details] patch possible fix!
Created attachment 112264 [details] mylyn/context/zip
Great catch Frank. The version is being set in BugzillaTaskDataHandler.initializeTaskData(). Rob, why are not all task data objects initialized through this method?
(In reply to comment #4) > Great catch Frank. The version is being set in > BugzillaTaskDataHandler.initializeTaskData(). Rob, why are not all task data > objects initialized through this method? I believe because the product isn't known so many of the attributes are not known. If this is the case the method should be renamed to something link initializeNewTaskData() but it doesn't appear to be in use which is a concern. yes, great catch Frank. I've applied your patch (and update ip log) but will need to look into this further.
The JIRA code has essentially the same structure. You can look at JiraTaskDataHandler for an example. Please extract the common parts of the initialization code into a method and set the task data version in a _single_ place.
Version now set in single location but some ugliness remains in BugzillaTaskDataHandler.getMultiTaskData(). Somewhat related is the oddity of where TaskData is being created in the BugzillaClient as well. More work to be done here.
(In reply to comment #7) > Version now set in single location but some ugliness remains in > BugzillaTaskDataHandler.getMultiTaskData(). Somewhat related is the oddity of > where TaskData is being created in the BugzillaClient as well. More work to be > done here. created bug#255132 to address this.