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 246710 - Generated installer creates shortcut that points to wrong executable for Windows, 64 bit systems
Summary: Generated installer creates shortcut that points to wrong executable for Wind...
Status: REOPENED
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal with 2 votes (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-26 21:51 UTC by unpocoloco
Modified: 2016-06-19 22:22 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NetBeans Installer Logs (149.15 KB, application/x-zip-compressed)
2014-09-10 00:16 UTC, unpocoloco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description unpocoloco 2014-08-26 21:51:18 UTC
Hi,

I have created a Maven NetBeans Platform Application (NBPA) (let's call it "SampleApp") and I generate installers by running the "nbm build-installers" goal.  This creates an .exe that the user can then run to automatically install my application. (In an ordinary NBPA, this would be "Package as -> Installers". Both have the same issue)

After the user runs the installer, a shortcut is placed on the user's desktop. However, for Windows 7 and Windows 8 64-bit systems, the shortcut is pointing to the wrong binary. It points to the 32-bit version. For instance, if I have an app named "SampleApp", the shortcut points to something like "C:\Program Files\sampleapp\sampleapp.exe" and NOT "C:\Program Files\sampleapp\sampleapp64.exe" as it should.  Both of these binaries DO exist in this folder.

This issue is creating a real problem for us because the application calls out various DLLs that are architecture specific (32-bit version will use 32-bit dlls, 64-bit should use 64-bit dlls).

The installer needs to create a shortcut that points to the correct binary based on the user's Operating System architecture.
Comment 1 Libor Fischmeistr 2014-08-30 16:15:49 UTC
Please attach the installer log. You can find it in <user profile>\.nbi\log
Comment 2 unpocoloco 2014-09-10 00:16:57 UTC
Created attachment 149099 [details]
NetBeans Installer Logs
Comment 3 unpocoloco 2014-09-10 00:17:38 UTC
Sorry for the delay. I installed a fresh copy of Windows 7, 64-bit on a clean hard drive and installed the latest Java JDK and NetBeans.  I created a Maven NBPA and a project called "SampleApp" as I previously described, which contains a module that has an editor TopComponent Window containing nothing other than a Button that says "Click Me!".  In other words, about as basic a scenario as I could get on as clean a system I could get.  The issue persists.

Attached is the installer log from this machine as requested.  If I can help further, please don't hesitate to ask.  Thanks!
Comment 4 Tirrel 2014-11-05 17:14:09 UTC
I have the same problem.
Have you resolved it?
Comment 5 tusharvjoshi 2015-02-07 18:49:55 UTC
I confirm this issue with NetBeans Platform 8.0.2 on Windows 7 64 bit.
Comment 6 hardyheroin 2015-02-10 02:14:18 UTC
I can also confirm this issue with NetBeans Platform 8.0.2 on Windows 7 64 bit.

But I can also say that Tirrel@netbeans.org posted the solution/workaround on StackOverflow:
http://stackoverflow.com/questions/26774879/resolved-generated-installer-creates-shortcut-that-points-to-wrong-executable

I have implemented this workaround myself and verified that it works.
Comment 7 aasmunds 2016-02-25 13:54:18 UTC
Hi. A quation to Tirrels solution. Where do I find or put the ConfigurationLogic.java. Do I need to compile it? Under .m2\repository\org\codehaus\mojo\nbm-maven-harness\8.0-beta there are jar and sha1 files. No java files. Maybe i need to put it to my project?
Is this the only workaround for this bug? It seems to be erroneous on NB 8.1 as well.
Hope for a solution quickly.
åsmund
Comment 8 phansson 2016-06-19 22:22:34 UTC
Posted some explanation and fix on SO.
http://stackoverflow.com/a/37910799