Member Avatar for jl.lakhnai

plese help me:)

  • 7 Contributors
  • 8 Replies
  • 197 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by turt2live

Dani AI

Generated

The simplest, most portable solution is an executable JAR: compile the classes, include a manifest that names the entry point (the class with public static void main), then run with the Java launcher. That is the standard, cross-platform approach suggested by and ; the JDK includes the jar tool to create archives and the java -jar launcher to run them. (docs.oracle.com)

A few practical clarifications and fixes to earlier advice (notably ): the manifest should be a plain text manifest (usually META-INF/MANIFEST.MF) containing a Main-Class: fully.qualified.Name header and must end with a newline. A minimal manifest looks like:

Main-Class: com.example.Main

After packaging, invoke the app with java -jar myapp.jar. The Java tutorial documents the manifest rules and the entry-point behavior. (docs.oracle.com)

Handling libraries and platform packaging: if the app depends on other JARs, either list them with the manifest Class-Path (keeps separate jars) or produce a single "fat/uber" JAR using build tools—Maven Shade or the Gradle Shadow plugin—so java -jar has everything it needs. If a native installer or bundled runtime is required (an actual .exe, MSI, DMG, DEB, etc.), prefer the JDK tools jlink/jpackage which create self-contained images/installers rather than opaque EXE-wrappers; third-party wrappers exist but are usually a last resort. (maven.apache.org)

Quick troubleshooting checklist (based on common thread issues): verify the manifest is present at META-INF/MANIFEST.MF, test from the command line with java -jar to capture stack traces, inspect the JAR with the jar tool if classes are missing, confirm the target JVM version matches the compiled bytecode, and use the IDE/export or a build script to reproduce the packaging reliably. These steps address the gaps and misconceptions raised earlier in the replies. (docs.oracle.com)

Recommended Answers

All 8 Replies

Member Avatar for harinath_2007

Did you forgot to write your question or just the Title is your question ?

Dont expect answers by posting like this.

You need to atleast type what exactly your problem...

Edited by harinath_2007 because: n/a
Member Avatar for NormR1

Be sure to explain the environment such as what IDE are you using.

Member Avatar for stultuske

by putting your project into a (valid) .jar file. you can do this by using the functionality of your IDE, but you don't need an IDE to create one. winrar (or a similar program) will do just fine.

Member Avatar for NormR1

The Java SDK has the jar command that will create a jar file.

Member Avatar for sam.udo

use a jar file,though it has so many steps......create a manifest file extension,the manifest file must contain the class file that has the main method,then isssue the following command in your command prompt window
jar-cmf jarfilename.jar manifestfilename classsesname
or
jar-cmf jarfilename.jar manifestfilename *.class
if u use the last one then ur manifest file and ur class files must be in the same directory

Member Avatar for sirlink99

if it is an application your IDE may provide an export as executable jar file option (I know eclipse does), or you can use a program called Java Launcher, which converts your applications into exes.

If it is an applet then you cannot convert it into an exe.

Member Avatar for stultuske

do not, I repeat NOT go and create an .exe file unless you have no other option.

if your employer demands an .exe file, and threatens to fire you, now this might be a reason I can understand (although you could also look at him with an "you kiddin' me?" expression on your face).

another reason I could understand, is that you have to develop a piece of code that you have to run under Windows in a certain (spooky?) way which only accept an .exe file.

but unless you're in such a situation, don't go there. a .jar file already is an executable, which can run by command line, or by being 'clicked', just like an exe file.

the main difference is, if you "settle" for a .jar file, you don't limit the users of your code to a particular (Windows) operating system. and this is not mentioning that a lot of 'create exe' apps out there create those exe's based on (who would have guessed?) a .jar file. so, since you'll already have the .jar file, you might as well stick with it :)

Member Avatar for turt2live

Like stultuske said,

if your employer demands an .exe file, and threatens to fire you, now this might be a reason I can understand

You can also use this tool: http://launch4j.sourceforge.net/

What it does is essentially change the extension and make it run correctly.

Even when my employer says "Make it an EXE file" I say "Why? A jar does the same thing"

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.