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.
Summary: | uninstallation fails. complaint that something was not found in the registry. | ||
---|---|---|---|
Product: | installer | Reporter: | pbelbin <pbelbin> |
Component: | NBI | Assignee: | Jiri Rechtacek <jrechtacek> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | lfischmeistr |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | install log file as requested |
Description
pbelbin
2013-02-14 17:21:18 UTC
I should mention that during installation, I did specify the --userdir option so that the installation would not see the other already installed (previously) glassfish instances. perhaps that has something to do with the problem? not sure. Not reproducible on linux - netbeans-7.3-linux.sh. (In reply to comment #1) > I should mention that during installation, I did specify the --userdir option > so that the installation would not see the other already installed (previously) > glassfish instances. Where? NetBeans installer doesn't have '--userdir' option I think. What do you see if you invoke netbeans-7.3-windows.exe --help on Windows command prompt? > perhaps that has something to do with the problem? Please, attach installation/uninstallation logs from C:\Users\<your-account>\.nbi\log (attach the two latest ones). It can help to investigate any possible problem. Thank you > not sure. Created attachment 131401 [details]
install log file as requested
log file as requested.
note, this log file is from the installation of the latest fcs proposal builds, and it was installed using a slightly different --userdir location.
regards,
peter
I have provided the log file as requested. note that the list of installer options I used is that which is available here: http://wiki.netbeans.org/NBICommandLineOptions which clearly lists the --userdir option. regards, peter I suppose you should specify --userdir while uninstall as well, because otherwise unistaller cannot find the right .nbi folder. (In reply to comment #6) > I suppose you should specify --userdir while uninstall as well, because > otherwise unistaller cannot find the right .nbi folder. Oh, sorry, now from the log I see you've done it. Am I right? I tried to reproduce but was unsuccessful. The uninstallation with custom userdir passed. (In reply to comment #4) > Created attachment 131401 [details] > install log file as requested > > log file as requested. > > note, this log file is from the installation of the latest fcs proposal builds, > and it was installed using a slightly different --userdir location. > > regards, > peter Thanks. But we need the uninstallation log (it means the latest one) too. (In reply to comment #5) > I have provided the log file as requested. > > note that the list of installer options I used is that which is available here: > > http://wiki.netbeans.org/NBICommandLineOptions > > which clearly lists the --userdir option. Oops, it's just a option documented on Web only for developers with NBI engine, but the common IDE users. I don't see why it's tracked as P1 then. > > regards, > peter hold on there. just because you have been unable to reproduce it does not mean the issue can be swept under the rug. the value of the --userdir is this: it's the only way I know of to allow a full install of content from the installation package, without the installer seeing that another instance of glassfish is installed already. I may be a bit paranoid or overly cautious about this aspect, but, I understand that when it comes to glassfish, that when netbeans installs it (or, perhaps rather, creates a domain) that there are some customizations that are done to glassfish over and above what you would get if you stick with the glassfish.zip directly obtainable from the glassfish download site. Also, the customizations may change from one version of netbeans to another. so, I really don't want my glassfish instances getting mixed up due to having two or more versions of NetBeans knowing about/messing with the one instance of glassfish installation. the netbeans installer, if run without any options, detects that glassfish is there, and *will not allow* the user to install another instance of it. now. the fact that you've been able to install and uninstall is great. but, you have not shared what value you used for your --userdir command option for me to be able to test with to see if I can reproduce your success. please do, and I'll give it a try. until then, as far as I'm concerned, this is still broken. and, as you should be aware, when you go into the windows add/remove programs tooling, you do not have the option of specifying any command line options. the installer should be (and seeming is) capturing what the --userdir option at installation was, and re-using that information during the uninstall. I am certainly not specifying it when I try to uninstall. there is no way to do so. unless you're referring to manually running the uninstaller app and giving there the --userdir option? and, are you testing with Windows 7 x64? I don't know, but that may make a difference. best regards, peter (In reply to comment #11) > I am certainly not specifying it when I try to uninstall. there is no way to > do so. > > unless you're referring to manually running the uninstaller app and giving > there the --userdir option? In this case there is nothing to solve. If you run the installer with the userdir specified, you also have to run the unistaller with the same userdir parameter to let the uninstaller find all necessary files to pass the unistallation. It's the same like when you run the installer: unistaller.exe --userdir <nbi folder> And you have to do it manually from the command line... Try it and you will see, that everything is ok. Thanks Ok. thank you for clarifying. I tried the manual uninstall.exe --userdir ${path-given-at-install} and yay! it does work. I don't recall ever having to run the uninstall manually in the past to achieve the desired uninstallation, but at least this is workable. ie: I think there's still something broken here, but, I agree it is not a show stopper any longer. all the best, peter |