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 26388 - Support of upgrade of settings between 3.4 and 4.0 projects
Summary: Support of upgrade of settings between 3.4 and 4.0 projects
Status: CLOSED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 3.x
Hardware: PC Windows 3.1/NT
: P1 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords: API
Depends on: 27379
Blocks: 26610 27141 27170
  Show dependency tree
 
Reported: 2002-08-08 15:44 UTC by Pavel Buzek
Modified: 2003-12-11 14:25 UTC (History)
3 users (show)

See Also:
Issue Type: TASK
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 Pavel Buzek 2002-08-08 15:44:15 UTC 
The task is to design and implement support for transition of settings from the 3.4 project into 
a 4.0 project. This is a part of upgrade scenario for projects between 3.4 and 4.0. If a module 
decides to start using the new projects settings framework (put settings into settings contexts 
of the Project and/or ProjectObjects) then there should be some support for migrating the 
values of these settings from 3.4 projects into 4.0. In general this cannot be done without 
cooperation of the module. The format of settings is not known, the transition may be more 
complex then just moving the value since the structure of settings may change, etc. 
Therefore the module should be able to provide its implementation of upgrade for its settings 
and register it in the IDE.
Comment 1 Pavel Buzek 2002-08-08 16:01:59 UTC 
some API may be needed for modules to register the convertors
Comment 2 Petr Nejedly 2002-08-08 16:37:16 UTC 
This is not limited to the new project implementation specific changes
to the settings. It can also be reused by modules which are going
to migrate their settings from SystemOption subclass to other
class and/or moving them out of the Services lookup.
Comment 3 Jaroslav Tulach 2002-08-19 13:40:25 UTC 
We have thought about problem of moving settings into a file with
different location (but still on default FS). The plan was to specify
(as attribute of the new settings file the location of the old). The
InstanceDataObject itself should check this attribute, read its value,
test if such file exists (probably using JNDI) and if so, read it,
save the new file and delete the old.

The convertion of the format would be responsibility of each module:
The read would initialize the module's settings code and the save
would store the values into new format.
Comment 4 Pavel Buzek 2002-11-08 12:08:51 UTC 
Removing from milestone 4. It is questionable if we need it at all.
Comment 5 Pavel Buzek 2002-11-29 09:13:13 UTC 
We will not imlement upgrade of project settings from 3.x except for import of mounted 
filesystems from 3.x projects [#28570]. Closing this issue.
Comment 6 Pavel Buzek 2003-07-02 14:07:34 UTC 
i've verified all these issues
Comment 7 Pavel Buzek 2003-07-02 14:18:32 UTC 
closing all my verified issues