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.
We use the NBI installer to instal a custom application based on the NetBeans Platform. The installer suggests a default installation location (path), but also provides a possibility to change it and install to a non-standard location. On the other hand, the installer also disallows installing the same product mutliple times. When this is attempted, the installers displays a message like: "Xyz is already installed at <path>. It is not possible to install it again. Click Exit to close this wizard." Problem: the <path> indicated above is always the default installation location path, not the path where the product has actually been previously installed. Normally (installation to default path) this is not a problem, but if the user installs to a non-standard location, then the message becomes confusing.
Hello, thank you for your report. I don't think this is a bug. This is the way how it works. It does not matter in what location the app is installed, the important is, that it has record in installer registry (<userhome>/.nbi folder). I agree with you, that this may not be the best solution and we should think about it, if there is the way how to do it better. So I'm changing issue type to enhancement.
Hello, and thanks for the response. I just want to clarify, that to me the issue was limited exclusively to what path is included in the string displayed to the user. I was not suggesting changing in any way the general logic, that only one registry record per (product+version) is allowed. To rephrase, the problem is purely cosmetic: imagine you have a "Turbo Foo 2.0" application, that by default installs into (on Linux for brevity) "/home/user/turboFoo-2.0". But user X didn't like the the default install location and installed Turbo Foo to "/home/user/apps/turboFoo-2.0" instead. The registry will contain that correct installation location. But when the user runs the installer again, he's going to see the text: "Turbo Foo 2.0 is already installed at /home/user/turboFoo-2.0 (...)" Now, this sentence is false. Turbo Foo 2.0 is already installed, yes, but it's installed at "/home/user/apps/turboFoo-2.0" not "/home/user/turboFoo-2.0" . In this sense I was thinking of it as a bug.