CODEWITHSUNDEEP
javanetbeansjarexecutablemanifest
Dani
Dani

Reputation: 4447

Producing executable jar in NetBeans

I'm using NetBeans 6.5 and for some reason it won't produce executable jar "out of the box".

I set my project to be the main project, defined main class in the project properties "run" menu and it works flawlessly when I press F6 to run it.

I looked at the manifest file and it indeed didn't define the main class there, and also omitted the library dependencies.



Am I missing something? Is there a way (other than manually altering the manifest file) to produce executable jar files?

EDIT: yes, I tried clean and rebuild and it produced the jar in the dist folder, still with the same manifest.mf

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 10.0-b23 (Sun Microsystems Inc.)

Upvotes: 20

Views: 81480

Answers (17)

myrho
myrho

Reputation: 441

If you are using the maven assembly plugin and want to build an executable jar with dependencies, you need to add this portion to the configuration of the maven-assembly-plugin section in your pom.xml:

<plugin>
  <artifactId>maven-assembly-plugin</artifactId>
  <configuration>
    <!-- ... -->
    <archive>
      <manifest>
        <mainClass>your.app.SampleClass</mainClass>
      </manifest>
    </archive>
  </configuration>
</plugin>

Source: Maven Assembly Plugin Usage

Upvotes: 6

vuongluis
vuongluis

Reputation: 1

Ok with neatbean you can do following steps below: 1. Right click name project choose item Set Configuration and Choose Customize
2. Choose Run and notice Main Class
3. Choose Browse and set class if you want to run. After you click ok.
4. Finish.

Upvotes: 0

Ken Lin
Ken Lin

Reputation: 1919

To manually force package creation with NetBeans IDE 8.0.2 ...

  1. In Project navigator, expand your <project> and right click Project Files / pom.xml
  2. Click Run Maven / Goals
  3. Type "package" in Goals field
  4. Click OK

The output window will then show (on Mac) ...

Building jar: /Users/<username>/NetBeansProjects/<project>/target/<project>-1.0-SNAPSHOT.jar

Upvotes: 0

Samuel Ventura
Samuel Ventura

Reputation: 19

In 7.3 just enable Properties/Build/Package/Copy Dependent Libraries and main class (depending on selected target) will be added to manifest when building.

Upvotes: 0

rarchibald
rarchibald

Reputation: 320

I just had the same problem in NetBeans 7.2.1 with a Maven Java Application project. Modify the pom.xml file to include the maven assembly plugin with one tweak to myrho's answer (needs to reference the predefined descriptor "jar-with-dependencies"):

<plugin>
    <artifactId>maven-assembly-plugin</artifactId>
    <version>2.4</version>
    <configuration>
        <descriptorRefs>
            <descriptorRef>jar-with-dependencies</descriptorRef>
        </descriptorRefs>
        <archive>
            <manifest>
                <mainClass>your.app.MainClass</mainClass>
            </manifest>
        </archive>
    </configuration>
    <executions>
        <execution>
            <id>make-assembly</id>
            <phase>package</phase>
            <goals>
                <goal>single</goal>
            </goals>
        </execution>
    </executions>
</plugin>

An alternate method is to build a Java Application project in NetBeans that doesn't use Maven. Select File -> Project Properties -> Build -> Packaging and check the "Copy Dependent Libraries" checkbox.

Upvotes: 8

l_39217_l
l_39217_l

Reputation: 2110

Goto the Files view. Create a manifest.mf in the root directory.

/project_folder
    build.xml
    manifest.mf(edit here)
    /dist
    /src
    /test
    /build

Upvotes: 0

kv.
kv.

Reputation: 61

Try this:

  1. Right click your project on the "Projects" panel, select "Properties"

  2. Click on "Run" in the new window.

  3. Edit the "Main Class:" field (click on Browse).

This way you will select the main class which is the entry point to your application and the Manifest will be created correctly.

Upvotes: 6

SMUsamaShah
SMUsamaShah

Reputation: 7890

Very simple, The .jar and .jad files are there in dist folder

I was also searching for answer and got this one from http://forums.netbeans.org/ptopic3465.html

Solved :)

Upvotes: 4

java.is.for.desktop
java.is.for.desktop

Reputation: 11216

Interesting information might be here:

http://wiki.netbeans.org/FaqNoMainClass

Upvotes: 0

ivan_ivanovich_ivanoff
ivan_ivanovich_ivanoff

Reputation: 19453

A better solution:

Edit nbproject/project.properties and add the entry:

manifest.file=manifest.mf

manifest.mf should be in project's root and contain just:

Manifest-Version: 1.0
X-COMMENT: Main-Class will be added automatically by build

Works. Tested.

Upvotes: 0

ivan_ivanovich_ivanoff
ivan_ivanovich_ivanoff

Reputation: 19453

I had the experience, that the build process is different, depending on the project type.

I suppose, you've created "Java Class Library" project.

So just create a "Java Application" project, then merge all classes to it.

Then, Netbeans will not override, but enhance the "manifest.mf" into the JAR.

Of course, it's a stupid Netbeans bug. Of course it should be possible to add main classes afterwards.

EDIT: Please see my other answer. It's easier.

Upvotes: 0

Xaerxess
Xaerxess

Reputation:

Maybe you created Java Project with Existing Sources instead of Java Application?

I had similar problem and creating new Java Application and then manually copying src files solved the problem - everything worked "out of the box".

Upvotes: 1

Jeff
Jeff

Reputation:

I actually came across this page after running into the same issue, I edited the manifest.mf file but the changes weren't showing up in the jar MANIFEST.MF file. I found the issue that I was having and thought I would pass along the information just in case it's relevant.

What I was doing wrong was I didn't have the project I was working on set as the main project, so while I was editing the the correct manifest, I was compiling the wrong project.

So I suppose the short of the story did you check and see if you have the correct project selected for the manifest.mf file you are editing?

Upvotes: 1

marktucks
marktucks

Reputation: 1771

If you clean and build your project it should create the jar in the "dist" directory.

It should create the manifest.mf at the top level of your project directory.

Upvotes: 1

James Kingsbery
James Kingsbery

Reputation: 7496

Another approach entirely is to develop, run unit tests, etc. in NetBeans but then use a maven or ant script to do your "real" build. It seems like these kinds of build tools give you more control over how things are built, and it also lets you automate builds.

For maven, you can add entries to the manifest easily using the maven jar plugin:

http://maven.apache.org/plugins/maven-jar-plugin/

Upvotes: 0

Rogier
Rogier

Reputation: 1240

Strange indeed, it should do it out of the box including the classpath.

Did you upgrade from a previous version? When upgrading, NB will upgrade the project files but sometimes this migration is not done well and this kind of scenario's pop up. Just close the project, rename the nbproject dir to nbproject_old and do new project -> Java project with existing sources. Set the main class again and add dependencies and try again.

Upvotes: 0

John Ellinwood
John Ellinwood

Reputation: 14531

Did you clean the project and rebuild? It sound like you're doing it right. Heres some references just in case:

http://www.velocityreviews.com/forums/t141385-how-to-create-executable-jar-in-netbeans-ide.html http://dr.berkeley.edu/REM/wiki/index.php/Making_a_Java_executable_jar_in_Netbeans

Upvotes: 2

Related Questions