Create true Windows applications from your Java code by simply dragging a jar file to this Executor?s icon and it immediately creates an EXE file. This lets you distribute your Java apps as genuine Win32 binary executables. Strings within the Win32 app even let you customize the Java virtual machine created to run your application. You can pass arguments such as ""-verbose:gc"" or ""-Xprof"" or set runtime properties with the ""-D"" option. You can also pass arguments to your program that will be appended to arguments supplied by the user from the command line or drag-and-drop.
Quick and easy conversion of java "jar" files to windows Executable format.
Cons
Some of the documentation for changing windows resources could be spruced up, and it took some digging to discover how to create an application icon for the executable that didn't cause the executable to crash. I found the companion program WinExecutor more usefull.
Summary
Does what it is intended, great instructions
Pros
Cons
Summary
This let me build a replacement for instant saxon for MSJVM-less Windows installations. I was able to include the JVM I wanted to use, adjust resources to access it, and move on. Reviewer Howard is providing an uninformed negative review. Why is this better than JBuilder? Well I don't write Java, I just wnat to run java apps quickly, sanely, with a simple call, double click, or drag-and-drop. READ the instructions.
students used successfully immediately
Pros
Cons
Summary
I teach AP Computer Science, and my high school students adapted to the demo version of this product like a duck to water. The only issue was packaging a .jar file correctly in the first place, but that is not the province of this product.
It Works
Pros
Cons
Summary
My life would be a lot easier if all products worked as well as Executor. It's easy to use and fast.
If you're looking for a utilty to make an .exe out of your executable .jar, look no further.
Pros
Cons
Summary
I take it back
Pros
Cons
Summary
I just ran the executables I created using this program on a machine that doesn't have a Java Runtime Environment, and they didn't run because the machine doesn't have a JRE. Arghhh, doesn't that defeat the purpose???
it works
Pros
Cons
Summary
I've been looking for something as simple as this, and I found it. It works (although I only did limited testing)
Better than JBuilder
Pros
Cons
Summary
JBuilder itself isn't free, and the free personal edition is for non-commercial use only.
Executor is $25 for a corporate site license with no restrictions on how many executables you create or where they are distributed.
Plus it's more flexible, because you can easily integrate it with your build scripts and systems without having to fire up JBuilder to run a wizard.
Plus you can customize where Executor looks for the Java VM and have control over which versions are supported. JBuilder only supports whatever is listed in the Windows Registry.
And Executor did get high marks for ease of use!
Disclaimer: I am the author of the program.
JBuilder can do it!
Pros
Cons
Summary
Why should I pay $20 for a thing that JBuilder can do for free?