This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 182118 - [69cat] 'Open Recent Projects' lost the correct projects recently closed
Summary: [69cat] 'Open Recent Projects' lost the correct projects recently closed
Status: VERIFIED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jesse Glick
URL:
Keywords: REGRESSION
: 182554 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-03-16 14:29 UTC by Michel Graciano
Modified: 2010-03-23 12:35 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Michel Graciano 2010-03-16 14:29:41 UTC 
[ BUILD # : ac7e616ba291 ]
[ JDK VERSION : 1.6.* ]

Well, I can't determine correct steps to reproduce it but to make it happens is
easy, just open some projects, I tested with 4. After open all these projects,
start to close some of them and reopen them from 'Open Recent Projects' option.
After few attempts some opened projects will be listed at 'Open Recent
Projects' list and the others which should be there will be lost. I will file
this as P1 since is a regression for a feature I use all day long.
One more detail is that, after the first time the problem shows up, it just go
worse, even restart the IDE doesn't fix the problem temporarily.
Comment 1 Jesse Glick 2010-03-16 16:55:52 UTC 
Seems to be reproducible. I don't know of any recent changes in these files except 2903a584765f, which was over a month ago and anyway does not look related to Recent Projects.

Not a P1 when there is a trivial workaround: open desired projects from File > Open Project.
Comment 2 Michel Graciano 2010-03-16 17:08:38 UTC 
No problem about priority, looks fair P2. BTW, 6.8 works fine and I faced it last week when I started to use daily builds for my daily work, where I use this feature a lot.
Comment 3 Jesse Glick 2010-03-16 17:38:16 UTC 
Seems to be due to my own 0c30b6632f78 (made right after 6.8 was branched); careless conversion of a for-loop. Surprising that this was not reported before. core-main #817d13788f13
Comment 4 Michel Graciano 2010-03-16 18:05:32 UTC 
Looks like it is not so much used... :(
Thanks for your fix, I will test it as soon as it is integrated with main repo.
Comment 5 Michel Graciano 2010-03-18 13:06:10 UTC 
v. 100317-4f4e9483a9f0
Comment 6 Jesse Glick 2010-03-23 12:35:49 UTC 
*** Bug 182554 has been marked as a duplicate of this bug. ***