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 121194 - Project options clobbered after using update center
Summary: Project options clobbered after using update center
Status: RESOLVED DUPLICATE of bug 120875
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P1 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-05 15:35 UTC by octaviant
Modified: 2007-11-06 14:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screen shot (394.73 KB, image/png)
2007-11-05 15:38 UTC, octaviant 		Details
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 octaviant 2007-11-05 15:35:08 UTC 
After a fresh installation, I used the Update center to get the Mercurial, Collaboration, REST and Module Manager
plugins. After the update, the only projects available were: C++ & Standard. See attached screen shot.
Comment 1 octaviant 2007-11-05 15:38:25 UTC 
Created attachment 52527 [details]
Screen shot
Comment 2 octaviant 2007-11-05 15:40:20 UTC 
Workaround: clean user dir
Comment 3 Marian Mirilovic 2007-11-05 18:20:15 UTC 
Just to be sure I followed your steps : 
- fresh installation
- run the IDE against existing userdir

Am I missing anything ? Could you please attach the log file ?

I tried fresh installation and ran the IDE against the new userdir and it works for me in NB Dev (200711040000). 

BTW: Octavian you are using old build. Anyway reassign to autoupdate for evaluation.
Comment 4 Marian Mirilovic 2007-11-06 13:56:05 UTC 
I spoke with Jirka Rechtacek and we found the key step to reproduce this bug. If you run such old build , the autoupdate
will warn you about the existing updates of your installed modules, so you had to do update of these modules (not just
installing above mentioned ones). 
This case is reproducible in Dev builds, just because we are connecting to the same update center during the whole
release cycle (that is built daily from the fresh sources). 
Anyway this is working right now, just because Jirka implemented "check for dependent modules" last week, I can't find
the appropriate issue. Jirka ?
Comment 5 Jiri Rechtacek 2007-11-06 14:05:02 UTC 
It's duplicate of issue 120875, already fixed in NB6.

*** This issue has been marked as a duplicate of 120875 ***