Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368088

Summary: nonexistent files from imported preferences and tasks reappear every restart
Product: [Eclipse Project] Platform Reporter: David M. Karr <davidmichaelkarr>
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug
Attachments:
Description Flags
Eclipse preferences exported from work laptop and imported on home laptop none

Description David M. Karr CLA 2012-01-07 13:47:00 EST 
Build Identifier: M20110909-1335

I believe I reported this last year, but I believe it was rejected.  It's still happening, so I'm going to try again.

I exported the Eclipse preferences and Mylyn tasks from my work laptop and imported them on my home laptop.  When I restarted Eclipse there were several editor views for files from my work laptop, but the files don't exist on my home laptop, so there was nothing to display.  I deleted those views, but when I restarted Eclipse again, they just reappeared.

This has continued to happen since the initial occurrence.

It seems likely this is a Mylyn problem, but that's just a guess.

I'll attach my Eclipse preferences and the Mylyn tasks export file that I imported.

Looking in the preferences file, I see occurrences of the nonexistent file names associated with Mylyn properties.

Reproducible: Always
Comment 1 David M. Karr CLA 2012-01-07 13:47:55 EST 
Created attachment 209167 [details]
Eclipse preferences exported from work laptop and imported on home laptop
Comment 2 David M. Karr CLA 2012-01-07 13:49:47 EST 
Actually, I have a feeling I never imported the Mylyn tasks.  That wouldn't have made any sense.
Comment 3 Eclipse Genie CLA 2019-09-27 15:12:34 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.