Community
Participate
Working Groups
Configuration: Eclipse Integration build with Mylyn 3.4 (3.4.0.v20100608-0100-e3x to be specific). Repository: bugs.eclipse.org I update Eclipse to latest I-build using Help -> Check for updates This would cause Mylyn to forget the values 3.7 and 3.7 Mx. It shows 4.0 entry directly after 3.6.x entries for the "Milestone" attribute. What generally fixes it? 1. Revalidating credentials on Task Repository view 2. Hitting "Update Attributes from Repository" couple of times. 3. Restart Eclipse Running Step 1 to 3 in random order fixes the problem. I am not sure problem is with p2 or Mylyn. But usecase-wise Mylyn is what fails.
Let's track this on bug 320978. It boils down to the same problem that you ended with a stale repository configuration. I don't think this is related to the p2 update but coincidence. *** This bug has been marked as a duplicate of bug 320978 ***
I would like to reopen this one as it is quite different from bug 320978 (which is about blocked UI). Adding Prakash who faced similar problem - vanishing attributes post I-build update. So I doubt its just coincidence. Also, I have been facing problem at least since Eclipse 3.6 M3 (thats around when I started using Mylyn more regularly).
Fair enough, then let's track the Bugzilla related problem here. From bug 320978 comment 3: The repository configuration attributes are regularly refreshed in the background. If you want to manually trigger a refresh in the background you can use the popup menu in the Task Repositories view. Note that bugs.eclipse.org mirrors the configuration which can sometimes cause a delay when new values are added to the configuration: http://wiki.eclipse.org/index.php/Mylyn_FAQ#Why_are_my_updated_repository_attributes_not_showing_up.3F . In your case it sounds like you keep getting a stale configuration which causes values to get lost. bug 320978 comment 4: The link https://bugs.eclipse.org/bugs/config.cgi redirects me to http://d2u376ub0heus3.cloudfront.net/arch/config.xml I do not have any extension installed. Only these two features Mylyn Connector: Bugzilla 3.4.0.v20100608-0100-e3x org.eclipse.mylyn.bugzilla_feature.feature.group Mylyn Task List (Required) 3.4.0.v20100608-0100-e3x org.eclipse.mylyn_feature.feature.group
The problem is two fold: 1) As suspected, the configuration on the mirror that you are being redirected to is stale. I have filed bug 321060 to address that. 2) Even if you happen to get a current copy from download.eclipse.org the next (automatic) update might still replace it with a stale one. The update mechanism only verifies that the ETag is different but does not check the last modified time stamp. Since there is a good chance that a mirrored config.xml files gets stale I think it's worth checking the Last-Modified header and to only proceed with an automatic update if the requested copy is actually newer. A manual update should always force an update like it does now. Rob, do you have time to look into this for 3.4.1?
Thanks for a prompt investigation.
Created attachment 176637 [details] comitted patch Please verify
Created attachment 176638 [details] mylyn/context/zip
Please reopen if you find any problem.
Sorry I did not see that the TargetMilestone is 3.4.2. My patch is only in HEAD. Steffen, can you do the backport?
Created attachment 178001 [details] backported patch
I have backported the changes. I changed the way the dates are parsed to use the DateUtil class from HttpClient. Can you forward port that to head so we have same implementation in both branches?
Created attachment 178088 [details] forward port patch
Created attachment 178089 [details] mylyn/context/zip
I think we can close this now.
