Windows Vista || JDK 1.6.0_04 || Eclipse Web Tools Platform 2.0.1 (Eclipse 3.3.1), "http://www.w3.org/2001/XMLSchema-instance", "http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd", http://maven.apache.org/shared/maven-archiver/index.html. How do I build a jar file that contains its dependencies. In JavaSW, an executable jarW file specifies its main class in the MANIFEST.MF file in that jar file. Problem: no main manifest attribute, in "APPLICATION_NAME.jar" I think the maven-jar-plugin is ignored. Tutorial created using: The manifest does get built when I run maven myself. Code Strategies But in this case, since the file is from an application, i … you get “no main manifest attribute”. When building with Eclipse (STS 3.6.2.RELEASE / Luna 4.4.1) the eclipse Maven build puts no manifest (and no META-INF at all) into the jars that get published. message that is output to the console as a result of the execution of com.maventest.App. Where do I put resources in my maven project? We used maven-jar-plugin to handle jar content and manifest configuration, specially adding a Main-Class property to MANIFEST.MF file to specify the project main class. There is no mention of a Main-Class ! If we perform a "mvn clean package" to build the project's jar file and then examine the MANIFEST.MF file that is generated in the jar file at META-INF/MANIFEST.MF, we see that it contains the following: I'll open a command prompt and go to the directory containing the jar file. This class is the one with the main method. Same issue with “Pivotal tc Server v3.0” and with Tomcat 7. Copyright © 2014 no main manifest attribute, in “app.jar” Normally, if I had created the program myself, I would have added a main class attribute to the manifest file. MANIFEST.MF file in generated jar file Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: Cakes Build-Jdk: 1.6.0_04 Main-Class: com.maventest.App I'll open a command prompt and go to the directory containing the jar file. Description: This tutorial describes how to specify a main class in the MANIFEST.MF file that gets automatically generated for a maven jar project. How do I add my own manifest file to a jar file? | Template: Free CSS Templates In order to run the main method from our jar, we need to mention it inside the ‘Main-Class’ property of the manifest file (mainClass attribute in POM.xml in case of Mavenized application) which needs to be bundled with the code as well. | Contact. If I attempt to execute the generated jar file via "java -jar aproject-1.0-SNAPSHOT.jar", we see the "Hello World!" Other entries can be added to the MANIFEST.MF as well via key-value pairs in the section: How do I specify a main class in the manifest of my generated jar file? Below the aim of the property : This snippet configures a special resource transformer which sets the Main-Class entry in the MANIFEST.MF of the shaded JAR. java -jar yourjar.jar my.package.Main. This happens because the project is being built by Maven and the Main Class you specified in the Netbeans properties is not exported by Netbeans to Maven’s pom.xml file; in other words: Netbeans knows what your main class is but Maven doesn’t. For a mavenSW project that features "jar" packaging, we can specify the main class for the MANIFEST.MF file by specifying it in our pom.xml, as shown here: This specifies that the com.maventest.App class in the project is the main class that should be executed if someone attempts to execute the jar file. Additional options that can be configured for the Maven Archiver can be found at http://maven.apache.org/shared/maven-archiver/index.html. When you run self-executable jar, java will look for the Main-Class in MANIFEST.MF file located under META-INF folder. If it is not able to find an entry,then it will complain with Unable to execute jar- file: “no main manifest attribute”.. MANIFEST.MF contains information about files contained in the Jar file.