Bug 290599 - [api] support partial updating of repository configuration
Summary: [api] support partial updating of repository configuration
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: 3.3   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 290490
  Show dependency tree
 
Reported: 2009-09-25 16:33 EDT by Steffen Pingel CLA
Modified: 2009-09-25 17:19 EDT (History)
1 user (show)

See Also:

Attachments
patch (8.57 KB, patch)
2009-09-25 16:40 EDT, Steffen Pingel CLA 		no flags Details | Diff
mylyn/context/zip (10.21 KB, application/octet-stream)
2009-09-25 16:40 EDT, Steffen Pingel CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steffen Pingel CLA 2009-09-25 16:33:56 EDT 
Updating the repository configuration can be expensive for large repositories. In order to support more fine-grained updating of configuration details AbstractRepositoryConnector.updateRepositoryConfiguration() should support a task parameter to limit the scope of an update.
Comment 1 Steffen Pingel CLA 2009-09-25 16:40:04 EDT 
Created attachment 148173 [details]
patch
Comment 2 Steffen Pingel CLA 2009-09-25 16:40:06 EDT 
Created attachment 148174 [details]
mylyn/context/zip
Comment 3 Steffen Pingel CLA 2009-09-25 16:41:52 EDT 
I have taken a similar approach as suggested on bug 290490 but limited the amount of changes required.
Comment 4 Pawel Niewiadomski CLA 2009-09-25 16:48:02 EDT 
Hi Steffen,
I started with a similar approach as in your patch - I used ITask as the argument for the new method but then I realized that it's not possible to directly get a project id from ITask, so I switched to TaskData.

Did I miss something? Is there any simple way to get project id for ITask?

Cheers,
Pawel
Comment 5 Steffen Pingel CLA 2009-09-25 17:14:08 EDT 
Yes, this will require storing the projectId on the task. I have commented on bug 290490 with a suggestion. The reason I do not want to include TaskData is for consistency with similar API methods and that TaskData may not be available in all cases, e.g. for web based tasks. 

I have filed bug 290606 to track further generalization of repository configuration handling.
Comment 6 Pawel Niewiadomski CLA 2009-09-25 17:19:25 EDT 
Thank you for the explanation.