how can i make ny software an executable file(.exe) i'm getting tired of using .jar
Printable View
how can i make ny software an executable file(.exe) i'm getting tired of using .jar
w w w.rgagnon.com/javadetails/java-0166.html'
seems good,
and you can also read java.sun.com/docs/books/tutorial/deployment/jar/manifestindex.html
JSmooth does a very good job of wrapping jar files in an .exe (For Windows only)
jsmooth.sourceforge.net
John
This is not a good idea, I mean deploy your application as an *.exe file. So it's only for Windows platforms. If you really want to do that, it's fine. But if you can make your application work on any platform really nice, as Java does.
Deploying as jar is much better. mtyoung given you two resources on that. The second one is the best.
I'm also intersted because on *NIX platform is simple to execute .jar files, but on Windows it leads to some troubles, and some win users can find it difficult to set up their environment so that, when you double-click on executable jars, they get executed. Moreover you can't deploy a jar with its own icon. Win users are not used to that, they automatically associate a program with an icon, not a command...
@akinpam
If your target customer can use an internet connection, why don't you try Java WebStart?
JSmooth allows you to select an icon, and also specify a particular java version to run with. Many commercial applications are built with it so my recommendation still stands.
I agree with you that the .jar extension confuses many end users.
On the application page, center section check the "Use an embedded jar" checkbox and then browse to the jar file that contains the main class specified in the Applications section at the top of the page.
Also in the classpath text area, specify any other .jar files you need like
lib\log4j.jar
lib\jdom.jar
etc
I'm using version 0.9.9-7 of JSmooth
John
Why not just write a batch file that sets the environment and runs the jar? I do the same with shell scripts in unix...
You can and many developers do just that. I personally think the ugly command shell popping up is not very professional looking however. You would never see a commercial application pop up a command shell like that. But if you're doing in-house tooling, it is a very easy solution.
JSmooth also gives you dynamic binding to the jre. Unless you know where the end user installed the specific version of the jre you need for your app, you have to handle support calls instructing users how to find out what version of the jre is installed on their machine, where it's installed and walk them through editing the command file.
John
Always deploying and distributing the application as a single package is much fair to users. They really like that. Sending a bunch of files as a zip and ask to unzip and so on not make sense at all.
But yes, most of the developers use batch files execution in developments. Not sufficient for the end users.