When using a custom ISS file to build the setup.exe for my application and with 
the SignTool configured in my InnoSetup environment I get the following stack 
trace.  The SignTool uses the following command line which works perfectly on 
the generated setup exe if the custom ISS file is not used.  Has the packager 
been tested with the windows SignTool

"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\signtool" sign /f my.pfx /p 
pswd /t http://timestamp.verisign.com/scripts/timstamp.dll /v $f

Error on line 36 in 
C:\Users\Scott\AppData\Local\Temp\fxbundler4814242320236876040\images\win-exe.image\Examine-IT
 Pro.iss: Value of [Setup] section directive "SignTool" is invalid.
Compile aborted.
java.io.IOException: Exec failed with code 2 command [[C:\Program Files 
(x86)\Inno Setup 5\iscc.exe, 
/oC:\Users\Scott\Documents\TCR-Software\Examine-IT-POM\Examine-IT-Pro\target\jfx\native,
 
C:\Users\Scott\AppData\Local\Temp\fxbundler4814242320236876040\images\win-exe.image\Examine-IT
 Pro.iss] in 
C:\Users\Scott\AppData\Local\Temp\fxbundler4814242320236876040\images\win-exe.image
        at com.oracle.tools.packager.IOUtils.exec(IOUtils.java:165)
        at com.oracle.tools.packager.IOUtils.exec(IOUtils.java:138)
        at com.oracle.tools.packager.IOUtils.exec(IOUtils.java:132)
        at 
com.oracle.tools.packager.windows.WinExeBundler.buildEXE(WinExeBundler.java:697)
        at 
com.oracle.tools.packager.windows.WinExeBundler.bundle(WinExeBundler.java:366)
        at 
com.oracle.tools.packager.windows.WinExeBundler.execute(WinExeBundler.java:173)
        at 
com.zenjava.javafx.maven.plugin.NativeMojo.execute(NativeMojo.java:344)
        at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

Reply via email to