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 14468 - inconsistent projects module after using 3.2 user dir
Summary: inconsistent projects module after using 3.2 user dir
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-16 09:35 UTC by David Simonek
Modified: 2003-07-01 14:19 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
log file (12.96 KB, text/plain)
2001-08-16 09:36 UTC, David Simonek 		Details
exit exception (4.22 KB, text/plain)
2001-08-16 09:37 UTC, David Simonek 		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 David Simonek 2001-08-16 09:35:31 UTC 
build NetBeans-dev-200108100740_qbe1, jdk 1.3

New build, point through -userdir option to older 3.2 user dir.
Project module didn't start well exception raised, "Workplace" node showed,
looked like projects module is disabled. But menu Projects is here, Project
Manager also. Cannot exit IDE, exception thrown.

Attached is the log with exceptions occurred during session.
Comment 1 David Simonek 2001-08-16 09:36:09 UTC 
Created attachment 2190 [details]
log file
Comment 2 David Simonek 2001-08-16 09:37:03 UTC 
Created attachment 2191 [details]
exit exception
Comment 3 Vitezslav Stejskal 2001-08-21 14:39:32 UTC 
x
Comment 4 Vitezslav Stejskal 2001-08-23 11:50:02 UTC 
This issue was a problem in backward compatibility of settings, it was 
caused by the XML Support module (written for 3.2) which doesn't have 
its XMLSupportSettings (descendant of SystemOption) correctly written 
(uses constructor for the initialization). Unfortunately it worked in 
3.2 and thus should in 3.3 as well, I have made appropriate changes in 
SharedClassObject and SystemOption classes to solve it and eliminate 
similar situations with other modules.
Comment 5 Milan Kubec 2002-01-18 08:19:20 UTC 
Verified.
Comment 6 Quality Engineering 2003-07-01 14:19:15 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.