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.
Installer (when upgrading) creates backup of previous installation folder and Upgrade Wizard should check this folder and use it for import. Cooperation is realy important.
Desired behavior should be following: Installer creates a backup of user settings and then does not move them into real location used by IDE. This means that installer will skip one current step. IDE when started detects this backup directory and offers to user to import from this dir.
Hmm. I think that current sitiation is this: Upgrade installer installs new version over the old one together with keeping the previous setings (Am I right Jiri?). So it does nearly the same as import wizard. When we skip the upgrade phase in the installer and then try to import from backuped previous version it should not work because there is not backuped the core.jar file, which is critical for import settings wizard to determine the previous version of IDE (am I right Jiri and Vita?). So the solution is that the upgrade installer should skip the upgrade phase and backup the core.jar too, so user can perform import using import wizard and all problems will be solved. Opinions?
Installer and Upgrade Wizard will cooperate on upgrade.properties file, which will be created by installer in the root of upgraded IDE. UW will read it and proceed import of settings from backup copy of system directory from previous version (created by installer). Me and Jirka will settle on the structure of upgrade.properties file.
Cooperation was implemented, Wizard imports settings from backup copy of the previous version made by Installer. Location of that copy as well as the version of previous IDE is stored in upgrade.properties file. Wizard looks for this file and procceds import automatically in silent mode (no GUI displayed) in case the file exists. Last Wizard's panel is displayed with additional info in case of errors. Fixed in dev, 3.2
verified, when user decides in the upgrade wizard to upgrade, settings are imported silently in the background and no interaction from the user is needed
Target milestone 3.2
Resolved for 3.4.x or earlier, no new info since then -> closing.