views:

264

answers:

1

Running on Linux, I've used launch4j to package an exe.

I copy the exe into my Windows 7 VM, and run it.

And nothing happens.

I run it with --l4j-debug, and nothing still happens (at least, if there's a log file, I cannot find it).

Is there some diagnostic technology that I'm missing here?

+1  A: 

Create a console version of your EXE (in the "Header" tab, change "Header type" from "GUI" to "Console") and run that from a CMD prompt.

Most likely you will see an exception message in the console, and that will explain why your app is failing to start.

finnw
@finnw I've run the same problem. However, I create exe wrapper using launch4j maven plugin (http://alakai.org/reference/plugins/launch4j-plugin-usage.html). When I define "console" target, the console windows is shown and quickly closed, .log file is generated but there is nothing special in it. Any advice?
dma_k
OK, I've solved the problem: I have removed `<classPath>` configuration entry and it worked smoothly. This is because I already have an "executable" jar, so I don't need to redefine mainclass/manifest.
dma_k