blocks|key|3588571|text|<build>
++<plugins>
++++<plugin>
++++++<artifactId>maven-assembly-plugin</artifactId>
++++++<configuration>
++++++++<archive>
++++++++++<manifest>
++++++++++++<mainClass>fully.qualified.MainClass</mainClass>
++++++++++</manifest>
++++++++</archive>
++++++++<descriptorRefs>
++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++</descriptorRefs>
++++++</configuration>
++++</plugin>
++</plugins>
</build>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3588572|然后你运行它|unstyled|3588573|mvn+clean+compile+assembly:single|3588574|编译目标应该在assembly之前添加:single，否则您自己的项目上的代码将不包括在内。|3588575|请在评论中查看更多详细信息。|3588576|3588577|通常，此目标被绑定到构建阶段以自动执行。这确保了在执行mvn+install或执行部署/发布时构建JAR。|offset|length|style|CODE|3588578|<plugin>
++<artifactId>maven-assembly-plugin</artifactId>
++<configuration>
++++<archive>
++++++<manifest>
++++++++<mainClass>fully.qualified.MainClass</mainClass>
++++++</manifest>
++++</archive>
++++<descriptorRefs>
++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++</descriptorRefs>
++</configuration>
++<executions>
++++<execution>
++++++<id>make-assembly</id>+
++++++<phase>package</phase>+
++++++<goals>
++++++++<goal>single</goal>
++++++</goals>
++++</execution>
++</executions>
</plugin>|3588579|entityMap^0|0|0|0|0|0|0|R|B|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|Z|8|@]|9|@]|A|$B|C]]|$1|I|3|J|5|F|7|10|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|11|8|@]|9|@]|A|$]]|$1|M|3|-4|5|F|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|F|7|13|8|@$P|14|Q|15|R|S]]|9|@]|A|$]]|$1|T|3|U|5|6|7|16|8|@]|9|@]|A|$B|C]]|$1|V|3|-4|5|F|7|17|8|@]|9|@]|A|$]]]|W|$]]

<pre class="lang-xml prettyprint-override"><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;fully.qualified.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

and you run it with

<pre class="lang-xml prettyprint-override"><code>mvn clean compile assembly:single
</code></pre>

Compile goal should be added before assembly:single or otherwise the code on your own project is not included.

See more details in comments.

<hr>

Commonly this goal is tied to a build phase to execute automatically. This ensures the JAR is built when executing <code>mvn install</code> or performing a deployment/release.

<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;fully.qualified.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-assembly&lt;/id&gt; &lt;!-- this is used for inheritance merges --&gt;
 &lt;phase&gt;package&lt;/phase&gt; &lt;!-- bind to the packaging phase --&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|4435479|text|接受未回答的答案并对其进行重新格式化，我们有：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435480|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-jar-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++<mainClass>fully.qualified.MainClass</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++</configuration>
++++++++</plugin>
++++++++<plugin>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++<descriptorRefs>
++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++</descriptorRefs>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
</build>|code-block|syntax|javascript|4435481|接下来，我建议将其作为构建的自然部分，而不是显式调用。要使其成为构建中不可或缺的一部分，请将此插件添加到pom.xml并将其绑定到package生命周期事件。但是，有一个问题是，如果将此代码放入pom.xml中，则需要调用程序集目标，而如果从命令行手动执行，则需要调用'assembly:assembly‘。|offset|length|style|CODE|4435482|<project>
++[...]
++<build>
++++++<plugins>
++++++++++<plugin>
++++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++++<configuration>
++++++++++++++++++<archive>
++++++++++++++++++++++<manifest>
++++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++++<mainClass>fully.qualified.MainClass</mainClass>
++++++++++++++++++++++</manifest>
++++++++++++++++++</archive>
++++++++++++++++++<descriptorRefs>
++++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++++</descriptorRefs>
++++++++++++++</configuration>
++++++++++++++<executions>
++++++++++++++++++<execution>
++++++++++++++++++++++<id>make-my-jar-with-dependencies</id>
++++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++++<goals>
++++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++++</goals>
++++++++++++++++++</execution>
++++++++++++++</executions>
++++++++++</plugin>
++++++[...]
++++++</plugins>
++++[...]
++</build>
</project>|4435483|entityMap^0|0|0|1G|7|1T|7|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@$I|T|J|U|K|L]|$I|V|J|W|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

Taking Unanswered's answer and reformatting it, we have:

<pre class="lang-xml prettyprint-override"><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;fully.qualified.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

Next, I would recommend making this a natural part of your build, rather than something to call explicitly. To make this a integral part of your build, add this plugin to your <code>pom.xml</code> and bind it to the <code>package</code> lifecycle event. However, a gotcha is that you need to call the <code>assembly:single</code> goal if putting this in your pom.xml, while you would call 'assembly:assembly' if executing it manually from the command line.

<pre class="lang-xml prettyprint-override"><code>&lt;project&gt;
 [...]
 &lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;fully.qualified.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-my-jar-with-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 [...]
 &lt;/plugins&gt;
 [...]
 &lt;/build&gt;
&lt;/project&gt;
</code></pre>

blocks|key|4435580|text|如果您真的想将其他JAR内容重新打包到单个结果JAR中，另一个选择是Maven+Assembly+plugin。它通过<unpack>true</unpack>将所有内容解包和重新打包到一个目录中。然后你会有第二次遍历，把它装进一个巨大的罐子里。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4435581|Another+option+is+the+OneJar+plugin。这将在一个步骤中执行上述重新打包操作。|4435582|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/plugins/maven-assembly-plugin/|1|http://code.google.com/p/onejar-maven-plugin/^0|1N|L|Y|L|0|0|0|Z|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

Another option if you really want to repackage the other JARs contents inside your single resultant JAR is the <a href="http://maven.apache.org/plugins/maven-assembly-plugin/" rel="noreferrer">Maven Assembly plugin</a>. It unpacks and then repacks everything into a directory via <code>&lt;unpack&gt;true&lt;/unpack&gt;</code>. Then you'd have a second pass that built it into one massive JAR.

<a href="http://code.google.com/p/onejar-maven-plugin/" rel="noreferrer">Another option is the OneJar plugin</a>. This performs the above repackaging actions all in one step.

blocks|key|371005|text|Ken+Liu在我看来是对的。maven依赖项插件允许您展开所有依赖项，然后可以将这些依赖项视为资源。这允许您将它们包含在主工件中。程序集插件的使用创建了一个很难修改的辅助工件--在我的例子中，我想添加自定义清单条目。我的pom结果是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|371006|<project>
+...
+<build>
++<plugins>
+++<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-dependency-plugin</artifactId>
++++<executions>
+++++<execution>
++++++<id>unpack-dependencies</id>
++++++<phase>package</phase>
++++++<goals>
+++++++<goal>unpack-dependencies</goal>
++++++</goals>
+++++</execution>
++++</executions>
+++</plugin>
++</plugins>
++...
++<resources>
+++<resource>
++++<directory>${basedir}/target/dependency</directory>
++++<targetPath>/</targetPath>
+++</resource>
++</resources>
+</build>
+...
</project>|code-block|syntax|javascript|371007|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Ken Liu has it right in my opinion. The maven dependency plugin allows you to expand all the dependencies, which you can then treat as resources. This allows you to include them in the main artifact. The use of the assembly plugin creates a secondary artifact which can be difficult to modify - in my case I wanted to add custom manifest entries. My pom ended up as:

<pre><code>&lt;project&gt;
 ...
 &lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;unpack-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;unpack-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 ...
 &lt;resources&gt;
 &lt;resource&gt;
 &lt;directory&gt;${basedir}/target/dependency&lt;/directory&gt;
 &lt;targetPath&gt;/&lt;/targetPath&gt;
 &lt;/resource&gt;
 &lt;/resources&gt;
 &lt;/build&gt;
 ...
&lt;/project&gt;
</code></pre>

blocks|key|4435692|text|你可以使用maven-dependency-plugin，但是问题是如何创建一个可执行的JAR。要做到这一点，需要对Matthew+Franglen的响应进行以下更改(顺便说一句，从干净的目标开始使用依赖插件需要更长的构建时间)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435693|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<artifactId>maven-jar-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<mainClass>fully.qualified.MainClass</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++</configuration>
++++++++</plugin>
++++++++<plugin>
++++++++++++<artifactId>maven-dependency-plugin</artifactId>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>unpack-dependencies</id>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>unpack-dependencies</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++</plugins>
++++<resources>
++++++++<resource>
++++++++++++<directory>${basedir}/target/dependency</directory>
++++++++</resource>
++++</resources>
</build>|code-block|syntax|javascript|4435694|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use maven-dependency-plugin, but the question was how to create an executable JAR. To do that requires the following alteration to Matthew Franglen's response (btw, using the dependency plugin takes longer to build when starting from a clean target):

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;fully.qualified.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;unpack-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;unpack-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;resources&gt;
 &lt;resource&gt;
 &lt;directory&gt;${basedir}/target/dependency&lt;/directory&gt;
 &lt;/resource&gt;
 &lt;/resources&gt;
&lt;/build&gt;
</code></pre>

blocks|key|4435743|text|我不会直接回答这个问题，因为其他人以前已经这样做过，但我真的想知道将所有依赖项嵌入到项目的jar本身中是否是一个好主意。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435744|我明白这一点(部署/使用的简单性)，但这取决于您的poject的用例(可能还有其他选择(见下文))。|4435745|如果你完全独立使用它，为什么不呢？|4435746|但是，如果您在其他上下文中使用您的项目(如在webapp中，或者放在其他jar所在的文件夹中)，则您的类路径中可能有jar副本(文件夹中的jar副本，jar中的副本)。也许不是出价交易，但我通常会避免这样做。|4435747|一个很好的选择：|4435748|4435749|将您的应用程序部署为.zip+/+.war+:归档文件包含项目的jar和所有相关的jar；|unordered-list-item|4435750|使用动态类加载器机制(请参见Spring，或者您也可以轻松地自己执行此操作)来拥有项目的单个入口点(要启动的单个类-请参阅另一个答案的清单机制)，这将(动态地)将所有其他所需的jar添加到当前类路径中。|4435751|4435752|就像这样，最后只有一个清单和一个“特殊的动态类加载器main"，你可以这样开始你的项目：|4435753|java+-jar+ProjectMainJar.jar+com.stackoverflow.projectName.MainDynamicClassLoaderClass|code-block|syntax|javascript|4435754|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|15|8|@]|9|@]|A|$]]|$1|N|3|O|5|M|7|16|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|18|8|@]|9|@]|A|$]]|$1|S|3|T|5|U|7|19|8|@]|9|@]|A|$V|W]]|$1|X|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|Y|$]]

I won't answer directly the question as other have already done that before, but I really wonder if it's a good idea to embed all the dependencies in the project's jar itself.

I see the point (ease of deployment / usage) but it depends of the use case of your poject (and there may be alternatives (see below)).

If you use it fully standalone, why not.

But if you use your project in other contexts (like in a webapp, or dropped in a folder where other jars are sitting), you may have jar duplicates in your classpath (the ones in the folder, the one in the jars). Maybe not a bid deal but i usually avoid this.

A good alternative :

<ul>
<li>deploy your application as a .zip / .war : the archive contains your project's jar and all dependent jars ;</li>
<li>use a dynamic classloader mechanism (see Spring, or you can easily do this yourself) to have a single entry point of your project (a single class to start - see the Manifest mechanism on another answer), which will add (dynamically) to the current classpath all the other needed jars.</li>
</ul>

Like this, with in the end just a manifest and a "special dynamic classloader main", you can start your project with :

<pre><code>java -jar ProjectMainJar.jar com.stackoverflow.projectName.MainDynamicClassLoaderClass
</code></pre>

blocks|key|4435765|text|应该是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435766|<plugin>
++++<artifactId>maven-dependency-plugin</artifactId>
++++<executions>
++++++++<execution>
++++++++++++<id>unpack-dependencies</id>
++++++++++++<phase>generate-resources</phase>
++++++++++++<goals>
++++++++++++++++<goal>unpack-dependencies</goal>
++++++++++++</goals>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|4435767|解包必须在生成资源阶段，因为如果在包阶段，将不会包含在资源中。尝试干净的包，你就会明白了。|4435768|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

It should be like that:

<pre><code>&lt;plugin&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;unpack-dependencies&lt;/id&gt;
 &lt;phase&gt;generate-resources&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;unpack-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

Unpacking have to be in generate-resources phase because, if in package phase, will not be included as resources.
Try clean package and you'll see.

blocks|key|4435794|text|要从命令行本身创建可执行JAR，只需从项目路径运行以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435795|mvn+assembly:assembly|code-block|syntax|javascript|4435796|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

To create an executable JAR from command line itself just run the below command from the project path:

<pre><code>mvn assembly:assembly
</code></pre>

blocks|key|371202|text|使用maven-shade-plugin将所有依赖项打包到一个uber-jar中。它还可用于通过指定主类来构建可执行jar。在尝试使用maven-assembly和maven-jar之后，我发现这个插件最适合我的需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|371203|我发现这个插件特别有用，因为它合并了特定文件的内容，而不是覆盖它们。当存在跨jars具有相同名称的资源文件，并且插件尝试打包所有资源文件时，需要执行此操作|371204|请参见下面的示例|371205|++++++<plugins>
++++
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-shade-plugin</artifactId>
++++++++++++<version>1.4</version>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>shade</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<artifactSet>
++++++++++++++++++++++++
++++++++++++++++++++++++++++<excludes>
++++++++++++++++++++++++++++++++<exclude>bouncycastle:bcprov-jdk15</exclude>
++++++++++++++++++++++++++++</excludes>
++++++++++++++++++++++++</artifactSet>

+++++++++++++++++++++++++<transformers>
++++++++++++++++++++++++++++<transformer
++++++++++++++++++++++++++++++++implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++<mainClass>com.main.MyMainClass</mainClass>
++++++++++++++++++++++++++++</transformer>
++++++++++++++++++++++++++++
++++++++++++++++++++++++++++<transformer+
+++++++++++++++++++++++++++++++++implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++++++++++<resource>properties.properties</resource>
++++++++++++++++++++++++++++</transformer>
++++++++++++++++++++++++++++<transformer
++++++++++++++++++++++++++++++++implementation="org.apache.maven.plugins.shade.resource.XmlAppendingTransformer">
++++++++++++++++++++++++++++++++<resource>applicationContext.xml</resource>
++++++++++++++++++++++++++++</transformer>
++++++++++++++++++++++++++++<transformer
++++++++++++++++++++++++++++++++implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++++++++++<resource>META-INF/cxf/cxf.extension</resource>
++++++++++++++++++++++++++++</transformer>
++++++++++++++++++++++++++++<transformer
++++++++++++++++++++++++++++++++implementation="org.apache.maven.plugins.shade.resource.XmlAppendingTransformer">
++++++++++++++++++++++++++++++++<resource>META-INF/cxf/bus-extensions.xml</resource>
++++++++++++++++++++++++++++</transformer>
+++++++++++++++++++++</transformers>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>

++++</plugins>|code-block|syntax|javascript|371206|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|P|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Use the maven-shade-plugin to package all dependencies into one uber-jar. It can also be used to build an executable jar by specifying the main class. After trying to use maven-assembly and maven-jar , I found that this plugin best suited my needs. 

I found this plugin particularly useful as it merges content of specific files instead of overwriting them. This is needed when there are resource files that are have the same name across the jars and the plugin tries to package all the resource files

See example below 

<pre><code> &lt;plugins&gt;
 &lt;!-- This plugin provides the capability to package the artifact in an uber-jar, including its dependencies and to shade - i.e. rename - the packages of some of the dependencies. --&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-shade-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.4&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;shade&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;artifactSet&gt;
 &lt;!-- signed jars--&gt;
 &lt;excludes&gt;
 &lt;exclude&gt;bouncycastle:bcprov-jdk15&lt;/exclude&gt;
 &lt;/excludes&gt;
 &lt;/artifactSet&gt;

 &lt;transformers&gt;
 &lt;transformer
 implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"&gt;
 &lt;!-- Main class --&gt;
 &lt;mainClass&gt;com.main.MyMainClass&lt;/mainClass&gt;
 &lt;/transformer&gt;
 &lt;!-- Use resource transformers to prevent file overwrites --&gt;
 &lt;transformer 
 implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;properties.properties&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer
 implementation="org.apache.maven.plugins.shade.resource.XmlAppendingTransformer"&gt;
 &lt;resource&gt;applicationContext.xml&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer
 implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/cxf/cxf.extension&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer
 implementation="org.apache.maven.plugins.shade.resource.XmlAppendingTransformer"&gt;
 &lt;resource&gt;META-INF/cxf/bus-extensions.xml&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;/transformers&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;

 &lt;/plugins&gt;
</code></pre>

blocks|key|3589045|text|在包阶段之前，您可以使用依赖项插件在单独的目录中生成所有依赖项，然后将其包含在清单的类路径中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589046|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-dependency-plugin</artifactId>
++++<executions>
++++++++<execution>
++++++++++++<id>copy-dependencies</id>
++++++++++++<phase>prepare-package</phase>
++++++++++++<goals>
++++++++++++++++<goal>copy-dependencies</goal>
++++++++++++</goals>
++++++++++++<configuration>
++++++++++++++++<outputDirectory>${project.build.directory}/lib</outputDirectory>
++++++++++++++++<overWriteReleases>false</overWriteReleases>
++++++++++++++++<overWriteSnapshots>false</overWriteSnapshots>
++++++++++++++++<overWriteIfNewer>true</overWriteIfNewer>
++++++++++++</configuration>
++++++++</execution>
++++</executions>
</plugin>
<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-jar-plugin</artifactId>
++++<configuration>
++++++++<archive>
++++++++++++<manifest>
++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++<classpathPrefix>lib/</classpathPrefix>
++++++++++++++++<mainClass>theMainClass</mainClass>
++++++++++++</manifest>
++++++++</archive>
++++</configuration>
</plugin>|code-block|syntax|javascript|3589047|或者，使用${project.build.directory}/classes/lib作为OutputDirectory将所有jar文件集成到主jar中，但随后您将需要添加自定义类加载代码来加载jar。|offset|length|style|CODE|3589048|entityMap^0|0|0|5|12|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

You can use the dependency-plugin to generate all dependencies in a separate directory before the package phase and then include that in the classpath of the manifest:

<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-dependencies&lt;/id&gt;
 &lt;phase&gt;prepare-package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;${project.build.directory}/lib&lt;/outputDirectory&gt;
 &lt;overWriteReleases&gt;false&lt;/overWriteReleases&gt;
 &lt;overWriteSnapshots&gt;false&lt;/overWriteSnapshots&gt;
 &lt;overWriteIfNewer&gt;true&lt;/overWriteIfNewer&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;classpathPrefix&gt;lib/&lt;/classpathPrefix&gt;
 &lt;mainClass&gt;theMainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>

Alternatively use <code>${project.build.directory}/classes/lib</code> as OutputDirectory to integrate all jar-files into the main jar, but then you will need to add custom classloading code to load the jars.

blocks|key|4435948|text|用maven-+assembly+-plugin-2.2.1定位共享程序集文件有问题吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4435949|请尝试使用descriptorId配置参数，而不是descriptors/descriptor或descriptorRefs/descriptorRef参数。|4435950|它们都不能满足您的需要:在类路径上查找文件。当然，您需要将共享程序集所在的包添加到maven-+assembly+-plugin的类路径中(见下文)。如果您使用的是Maven2.x(而不是Maven3.x)，则可能需要在pluginManagement部分的最顶层父pom.xml中添加此依赖项。|4435951|有关更多详细信息，请参阅this。|offset|length|4435952|类:+org.apache.maven.plugin.assembly.io.DefaultAssemblyReader|4435953|示例：|4435954|++++++++
++++++++<plugin>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<version>2.2.1</version>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>make-assembly</id>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<descriptorId>assembly-zip-for-wid</descriptorId>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++++++<dependencies>
++++++++++++++++<dependency>
++++++++++++++++++++<groupId>cz.ness.ct.ip.assemblies</groupId>
++++++++++++++++++++<artifactId>TEST_SharedAssemblyDescriptor</artifactId>
++++++++++++++++++++<version>1.0.0-SNAPSHOT</version>
++++++++++++++++</dependency>
++++++++++++</dependencies>
++++++++</plugin>|code-block|syntax|javascript|4435955|entityMap|0|LINK|mutability|MUTABLE|url|http://svn.apache.org/repos/asf/maven/plugins/tags/maven-assembly-plugin-2.2.1^0|0|0|0|C|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|13|8|@]|9|@$H|14|I|15|1|16]]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|19|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z]]]]

Problem with locating shared assembly file with maven-assembly-plugin-2.2.1?

Try using descriptorId configuration parameter instead of descriptors/descriptor or descriptorRefs/descriptorRef parameters.

Neither of them do what you need: look for the file on classpath.
Of course you need adding the package where the shared assembly resides on maven-assembly-plugin's classpath (see below).
If you're using Maven 2.x (not Maven 3.x), you may need adding this dependency in top-most parent pom.xml in pluginManagement section.

See <a href="http://svn.apache.org/repos/asf/maven/plugins/tags/maven-assembly-plugin-2.2.1" rel="noreferrer">this</a> for more details.

Class: org.apache.maven.plugin.assembly.io.DefaultAssemblyReader

Example:

<pre><code> &lt;!-- Use the assembly plugin to create a zip file of all our dependencies. --&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.2.1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-assembly&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;descriptorId&gt;assembly-zip-for-wid&lt;/descriptorId&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;cz.ness.ct.ip.assemblies&lt;/groupId&gt;
 &lt;artifactId&gt;TEST_SharedAssemblyDescriptor&lt;/artifactId&gt;
 &lt;version&gt;1.0.0-SNAPSHOT&lt;/version&gt;
 &lt;/dependency&gt;
 &lt;/dependencies&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|371350|text|可以将以下内容添加到pom.xml中|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|371351|<build>
<defaultGoal>install</defaultGoal>
<plugins>
++<plugin>
++++<artifactId>maven-compiler-plugin</artifactId>
++++<version>2.3.2</version>
++++<configuration>
++++++<source>1.6</source>
++++++<target>1.6</target>
++++</configuration>
++</plugin>
++<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-jar-plugin</artifactId>
++++<version>2.3.1</version>
++++<configuration>
++++++<archive>
++++++++<manifest>
++++++++++<addClasspath>true</addClasspath>
++++++++++<mainClass>com.mycompany.package.MainClass</mainClass>
++++++++</manifest>
++++++</archive>
++++</configuration>
++</plugin>
++<plugin>
++++<artifactId>maven-assembly-plugin</artifactId>
++++<configuration>
++++++<descriptorRefs>
++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++</descriptorRefs>
++++++<archive>
++++++++<manifest>
++++++++++<mainClass>com.mycompany.package.MainClass</mainClass>
++++++++</manifest>
++++++</archive>
++++</configuration>
++++<executions>
++++++<execution>
++++++++<id>make-my-jar-with-dependencies</id>
++++++++<phase>package</phase>
++++++++<goals>
++++++++++<goal>single</goal>
++++++++</goals>
++++++</execution>
++++</executions>
++</plugin>
</plugins>
</build>|code-block|syntax|javascript|371352|之后，您必须通过控制台切换到pom.xml所在的目录。然后，您必须执行JAR+mvn程序集:单个，然后您的带有依赖项的可执行JAR文件将有望被构建。您可以在使用mavenproject1-1.0-SNAPSHOT-jar-with-dependencies.jar.+cd./切换到输出(目标)目录并使用类似于java+-jar+jar的命令启动jar时对其进行检查|371353|我用Apache+Maven+3.0.3对此进行了测试。|371354|entityMap^0|A|7|0|0|4B|S|0|0|S|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|P|$]]

You can add the following to your pom.xml:

<pre><code>&lt;build&gt;
&lt;defaultGoal&gt;install&lt;/defaultGoal&gt;
&lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
 &lt;configuration&gt;
 &lt;source&gt;1.6&lt;/source&gt;
 &lt;target&gt;1.6&lt;/target&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.3.1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;com.mycompany.package.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;com.mycompany.package.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-my-jar-with-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
&lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

Afterwards you have to switch via the console to the directory, where the pom.xml is located. Then you have to execute mvn assembly:single and then your executable JAR file with dependencies will be hopefully build. You can check it when switching to the output (target) directory with cd ./target and starting your jar with a command similiar to java -jar mavenproject1-1.0-SNAPSHOT-jar-with-dependencies.jar. 

I tested this with Apache Maven 3.0.3.

blocks|key|1048660|text|您可以结合使用maven-shade-plugin和maven-jar-plugin。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1048661|为了指定可执行jar的主类，maven-shade-plugin将您的类和所有依赖项打包到单个jar中，以指定可执行Jar的主类(请参见"Make+Jar+Executable").“一章中的Set+Up+The+Classpath|1048662|maven-jar-plugin的POM配置示例|1048663|++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-jar-plugin</artifactId>
++++++++++++<version>2.3.2</version>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++<mainClass>com.example.MyMainClass</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|1048664|最后，通过调用以下命令创建可执行jar：|1048665|mvn+clean+package+shade:shade|1048666|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/shared/maven-archiver/examples/classpath.html^0|7|I|Q|G|0|E|I|2O|K|0|0|0|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|I|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|J|3|K|5|L|7|1E|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|1F|8|@]|D|@]|E|$]]|$1|Q|3|R|5|L|7|1G|8|@]|D|@]|E|$M|N]]|$1|S|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|T|$U|$5|V|W|X|E|$Y|Z]]]]

You could combine the <code>maven-shade-plugin</code> and <code>maven-jar-plugin</code>.

<ul>
<li>The <code>maven-shade-plugin</code> packs your classes and all dependencies in a single jar file.</li>
<li>Configure the <code>maven-jar-plugin</code> to specify the main class of your executable jar (see <a href="http://maven.apache.org/shared/maven-archiver/examples/classpath.html" rel="noreferrer">Set Up The Classpath</a>, chapter "Make The Jar Executable").</li>
</ul>

Example POM configuration for <code>maven-jar-plugin</code>:

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.3.2&lt;/version&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;com.example.MyMainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

Finally create the executable jar by invoking:

<pre><code>mvn clean package shade:shade
</code></pre>

blocks|key|371460|text|我长期使用maven汇编插件，但我找不到使用"already+added,+skipping"解决这个问题的方法。现在，我使用了另一个插件--+。示例如下(mvn+package+build+jar)：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|371461|<plugin>
++++<groupId>org.dstovall</groupId>
++++<artifactId>onejar-maven-plugin</artifactId>
++++<version>1.3.0</version>
++++<executions>
++++++++<execution>
++++++++++++<configuration>
++++++++++++++++<mainClass>com.company.MainClass</mainClass>
++++++++++++</configuration>
++++++++++++<goals>
++++++++++++++++<goal>one-jar</goal>
++++++++++++</goals>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|371462|您需要为该插件添加存储库：|371463|<pluginRepositories>
++++<pluginRepository>
++++++++<id>onejar-maven-plugin.googlecode.com</id>
++++++++<url>http://onejar-maven-plugin.googlecode.com/svn/mavenrepo</url>
++++</pluginRepository>
</pluginRepositories>|371464|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2596655/how-do-i-surpress-maven-assembly-plugin-skipping-files-that-are-already-added-o^0|5|9|M|P|26|B|M|P|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|D]|$9|12|A|13|B|D]]|E|@$9|14|A|15|1|16]]|F|$]]|$1|G|3|H|5|I|7|17|8|@]|E|@]|F|$J|K]]|$1|L|3|M|5|6|7|18|8|@]|E|@]|F|$]]|$1|N|3|O|5|I|7|19|8|@]|E|@]|F|$J|K]]|$1|P|3|-4|5|6|7|1A|8|@]|E|@]|F|$]]]|Q|$R|$5|S|T|U|F|$V|W]]]]

Long used the maven assembly plugin, but I could not find a solution to the problem with <a href="https://stackoverflow.com/questions/2596655/how-do-i-surpress-maven-assembly-plugin-skipping-files-that-are-already-added-o"><code>"already added, skipping"</code></a>. Now, I'm using another plugin - <a href="http://code.google.com/p/onejar-maven-plugin/" rel="noreferrer">onejar-maven-plugin</a>. Example below (<code>mvn package</code> build jar):

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.dstovall&lt;/groupId&gt;
 &lt;artifactId&gt;onejar-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.3.0&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;configuration&gt;
 &lt;mainClass&gt;com.company.MainClass&lt;/mainClass&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;one-jar&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

You need to add repository for that plugin:

<pre><code>&lt;pluginRepositories&gt;
 &lt;pluginRepository&gt;
 &lt;id&gt;onejar-maven-plugin.googlecode.com&lt;/id&gt;
 &lt;url&gt;http://onejar-maven-plugin.googlecode.com/svn/mavenrepo&lt;/url&gt;
 &lt;/pluginRepository&gt;
&lt;/pluginRepositories&gt;
</code></pre>

blocks|key|4436089|text|maven-assembly-plugin对我来说工作得很好。我花了几个小时使用maven-dependency-plugin，却不能让它工作。主要原因是我必须在配置部分中显式地定义构件项，这些构件项应该按照documentation中所描述的那样包括在内。当你想像这样使用它的时候，有一个例子：mvn+dependency:copy，其中没有包含任何artifactItems，但它不工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4436090|entityMap|0|LINK|mutability|MUTABLE|url|http://maven.apache.org/plugins/maven-dependency-plugin/usage.html^0|44|J|2W|D|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

The maven-assembly-plugin worked great for me.
I spent hours with the maven-dependency-plugin and couldn't make it work. The main reason was that I had to define in the configuration section explicitly the artifact items which should be included as it is described in the <a href="http://maven.apache.org/plugins/maven-dependency-plugin/usage.html" rel="nofollow">documentation</a>. 
There is an example there for the cases when you want to use it like: <code>mvn dependency:copy</code>, where there are not included any artifactItems but it doesn't work.

blocks|key|4436137|text|对我有效的方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436138|++<plugin>
++++<artifactId>maven-dependency-plugin</artifactId>
++++<executions>
++++++<execution>
++++++++<id>unpack-dependencies</id>
++++++++<phase>prepare-package</phase>
++++++++<goals>
++++++++++<goal>unpack-dependencies</goal>
++++++++</goals>
++++++++<configuration>
++++++++++<outputDirectory>${project.build.directory}/classes</outputDirectory>
++++++++</configuration>
++++++</execution>

++++</executions>
++</plugin>


++<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-jar-plugin</artifactId>
++++<executions>
++++++<execution>
++++++++<id>unpack-dependencies</id>
++++++++<phase>package</phase>
++++++</execution>
++++</executions>
++++<configuration>
++++++<archive>
++++++++<manifest>
++++++++++<addClasspath>true</addClasspath>
++++++++++<classpathPrefix>lib/</classpathPrefix>
++++++++++<mainClass>SimpleKeyLogger</mainClass>
++++++++</manifest>
++++++</archive>
++++</configuration>
++</plugin>|code-block|syntax|javascript|4436139|我遇到了不寻常的情况，因为我的依赖是系统一：|4436140|<dependency>
++..
++<scope>system</scope>
++<systemPath>${project.basedir}/lib/myjar.jar</systemPath>
</dependency>|4436141|我已经修改了@user189057提供的代码:+1)+maven-classes+plugin在"prepare-package“阶段执行2)我将解包的classess直接提取到"target/classes”|4436142|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Something that have worked for me was:

<pre><code> &lt;plugin&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;unpack-dependencies&lt;/id&gt;
 &lt;phase&gt;prepare-package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;unpack-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;${project.build.directory}/classes&lt;/outputDirectory&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;

 &lt;/executions&gt;
 &lt;/plugin&gt;


 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;unpack-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;classpathPrefix&gt;lib/&lt;/classpathPrefix&gt;
 &lt;mainClass&gt;SimpleKeyLogger&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

I had extraordinary case because my dependency was system one:

<pre><code>&lt;dependency&gt;
 ..
 &lt;scope&gt;system&lt;/scope&gt;
 &lt;systemPath&gt;${project.basedir}/lib/myjar.jar&lt;/systemPath&gt;
&lt;/dependency&gt;
</code></pre>

I have changed the code provided by @user189057 with changes:
1) maven-dependency-plugin is executed in "prepare-package" phase
2) I am extracting unpacked classess directly to "target/classes"

blocks|key|3589390|text|请参阅executable-jar-with-maven-example+(GitHub)|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3589391|备注|3589392|这些利弊都是由Stephan提供的。|3589393|3589394|用于手动部署|3589395|最终jar.之外的|3589396|Pros|unordered-list-item|3589397|Cons+|3589398|依赖项|3589399|3589400|3589401|将依赖项复制到特定目录|3589402|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-dependency-plugin</artifactId>
++<executions>
++++<execution>
++++++<id>copy-dependencies</id>
++++++<phase>prepare-package</phase>
++++++<goals>
++++++++<goal>copy-dependencies</goal>
++++++</goals>
++++++<configuration>
++++++++<outputDirectory>${project.build.directory}/${project.build.finalName}.lib</outputDirectory>
++++++</configuration>
++++</execution>
++</executions>
</plugin>|code-block|syntax|javascript|3589403|使Jar可执行文件和类路径可识别|3589404|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-jar-plugin</artifactId>
++<configuration>
++++<archive>
++++++<manifest>
++++++++<addClasspath>true</addClasspath>
++++++++<classpathPrefix>${project.build.finalName}.lib/</classpathPrefix>
++++++++<mainClass>${fully.qualified.main.class}</mainClass>
++++++</manifest>
++++</archive>
++</configuration>
</plugin>|3589405|此时，jar实际上是可使用外部类路径元素执行的。|style|CODE|3589406|$+java+-jar+target/${project.build.finalName}.jar|3589407|创建可部署的归档文件|3589408|只有同级...lib/目录才能执行jar文件。我们需要使存档与目录及其内容一起部署。|3589409|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-antrun-plugin</artifactId>
++<executions>
++++<execution>
++++++<id>antrun-archive</id>
++++++<phase>package</phase>
++++++<goals>
++++++++<goal>run</goal>
++++++</goals>
++++++<configuration>
++++++++<target>
++++++++++<property+name="final.name"+value="${project.build.directory}/${project.build.finalName}"/>
++++++++++<property+name="archive.includes"+value="${project.build.finalName}.${project.packaging}+${project.build.finalName}.lib/*"/>
++++++++++<property+name="tar.destfile"+value="${final.name}.tar"/>
++++++++++<zip+basedir="${project.build.directory}"+destfile="${final.name}.zip"+includes="${archive.includes}"+/>
++++++++++<tar+basedir="${project.build.directory}"+destfile="${tar.destfile}"+includes="${archive.includes}"+/>
++++++++++<gzip+src="${tar.destfile}"+destfile="${tar.destfile}.gz"+/>
++++++++++<bzip2+src="${tar.destfile}"+destfile="${tar.destfile}.bz2"+/>
++++++++</target>
++++++</configuration>
++++</execution>
++</executions>
</plugin>|3589410|现在您有了分别包含jar和lib/*的target/${project.build.finalName}.(zip%7Ctar%7Ctar.bz2%7Ctar.gz)。|3589411|3589412|Apache+Maven程序集插件|3589413|3589414|3589415|Cons阴影插件不支持类重定位(如果类重定位为needed).|3589416|，请使用maven--|3589417|3589418|3589419|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-assembly-plugin</artifactId>
++<executions>
++++<execution>
++++++<phase>package</phase>
++++++<goals>
++++++++<goal>single</goal>
++++++</goals>
++++++<configuration>
++++++++<archive>
++++++++++<manifest>
++++++++++++<mainClass>${fully.qualified.main.class}</mainClass>
++++++++++</manifest>
++++++++</archive>
++++++++<descriptorRefs>
++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++</descriptorRefs>
++++++</configuration>
++++</execution>
++</executions>
</plugin>|3589420|你有target/${project.bulid.finalName}-jar-with-dependencies.jar。|3589421|3589422|Apache+Maven+Shade插件|3589423|3589424|3589425|Cons|3589426|3589427|<plugin>
++<groupId>org.apache.maven.plugins</groupId>
++<artifactId>maven-shade-plugin</artifactId>
++<executions>
++++<execution>
++++++<goals>
++++++++<goal>shade</goal>
++++++</goals>
++++++<configuration>
++++++++<shadedArtifactAttached>true</shadedArtifactAttached>
++++++++<transformers>
++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
++++++++++++<mainClass>${fully.qualified.main.class}</mainClass>
++++++++++</transformer>
++++++++</transformers>
++++++</configuration>
++++</execution>
++</executions>
</plugin>|3589428|你有target/${project.build.finalName}-shaded.jar。|3589429|3589430|onejar-maven-plugin|3589431|自2012.以来，不再主动支持|3589432|3589433|Cons+|3589434|3589435|3589436|3589437|<plugin>
+++
++<groupId>com.jolira</groupId>
++<artifactId>onejar-maven-plugin</artifactId>
++<executions>
++++<execution>
++++++<configuration>
++++++++<mainClass>${fully.qualified.main.class}</mainClass>
++++++++<attachToBuild>true</attachToBuild>
++++++++
++++++++
++++++++<filename>${project.build.finalName}-onejar.${project.packaging}</filename>
++++++</configuration>
++++++<goals>
++++++++<goal>one-jar</goal>
++++++</goals>
++++</execution>
++</executions>
</plugin>|3589438|3589439|Spring+Boot+Maven插件|3589440|3589441|3589442|Cons+|3589443|添加与弹簧和弹簧启动相关的潜在不必要的classes.|3589444|3589445|3589446|<plugin>
++<groupId>org.springframework.boot</groupId>
++<artifactId>spring-boot-maven-plugin</artifactId>
++<executions>
++++<execution>
++++++<goals>
++++++++<goal>repackage</goal>
++++++</goals>
++++++<configuration>
++++++++<classifier>spring-boot</classifier>
++++++++<mainClass>${fully.qualified.main.class}</mainClass>
++++++</configuration>
++++</execution>
++</executions>
</plugin>|3589447|你有target/${project.bulid.finalName}-spring-boot.jar。|3589448|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jinahya/executable-jar-with-maven-example|1|https://stackoverflow.com/users/363573/stephan^0|3|X|0|0|0|7|7|1|0|0|0|0|0|1|1|0|0|0|0|0|0|3|3|0|0|0|4|7|H|3|0|0|9|3|D|5|J|1M|0|0|0|0|0|0|0|0|0|0|2|1N|0|0|0|0|0|0|0|0|2|18|0|0|0|0|0|1|1|0|0|0|0|0|0|0|1|1|0|0|0|2|1D|0^^$0|@$1|2|3|4|5|6|7|3D|8|@]|9|@$A|3E|B|3F|1|3G]]|C|$]]|$1|D|3|E|5|6|7|3H|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|3I|8|@]|9|@$A|3J|B|3K|1|3L]]|C|$]]|$1|H|3|-4|5|6|7|3M|8|@]|9|@]|C|$]]|$1|I|3|J|5|6|7|3N|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|3O|8|@]|9|@]|C|$]]|$1|M|3|N|5|O|7|3P|8|@]|9|@]|C|$]]|$1|P|3|Q|5|O|7|3Q|8|@]|9|@]|C|$]]|$1|R|3|S|5|O|7|3R|8|@]|9|@]|C|$]]|$1|T|3|-4|5|6|7|3S|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|3T|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|3U|8|@]|9|@]|C|$]]|$1|X|3|Y|5|Z|7|3V|8|@]|9|@]|C|$10|11]]|$1|12|3|13|5|6|7|3W|8|@]|9|@]|C|$]]|$1|14|3|15|5|Z|7|3X|8|@]|9|@]|C|$10|11]]|$1|16|3|17|5|6|7|3Y|8|@$A|3Z|B|40|18|19]]|9|@]|C|$]]|$1|1A|3|1B|5|Z|7|41|8|@]|9|@]|C|$10|11]]|$1|1C|3|1D|5|6|7|42|8|@]|9|@]|C|$]]|$1|1E|3|1F|5|6|7|43|8|@$A|44|B|45|18|19]|$A|46|B|47|18|19]]|9|@]|C|$]]|$1|1G|3|1H|5|Z|7|48|8|@]|9|@]|C|$10|11]]|$1|1I|3|1J|5|6|7|49|8|@$A|4A|B|4B|18|19]|$A|4C|B|4D|18|19]|$A|4E|B|4F|18|19]]|9|@]|C|$]]|$1|1K|3|-4|5|6|7|4G|8|@]|9|@]|C|$]]|$1|1L|3|1M|5|6|7|4H|8|@]|9|@]|C|$]]|$1|1N|3|-4|5|6|7|4I|8|@]|9|@]|C|$]]|$1|1O|3|N|5|O|7|4J|8|@]|9|@]|C|$]]|$1|1P|3|1Q|5|O|7|4K|8|@]|9|@]|C|$]]|$1|1R|3|1S|5|6|7|4L|8|@]|9|@]|C|$]]|$1|1T|3|-4|5|O|7|4M|8|@]|9|@]|C|$]]|$1|1U|3|-4|5|6|7|4N|8|@]|9|@]|C|$]]|$1|1V|3|1W|5|Z|7|4O|8|@]|9|@]|C|$10|11]]|$1|1X|3|1Y|5|6|7|4P|8|@$A|4Q|B|4R|18|19]]|9|@]|C|$]]|$1|1Z|3|-4|5|6|7|4S|8|@]|9|@]|C|$]]|$1|20|3|21|5|6|7|4T|8|@]|9|@]|C|$]]|$1|22|3|-4|5|6|7|4U|8|@]|9|@]|C|$]]|$1|23|3|N|5|O|7|4V|8|@]|9|@]|C|$]]|$1|24|3|25|5|O|7|4W|8|@]|9|@]|C|$]]|$1|26|3|-4|5|6|7|4X|8|@]|9|@]|C|$]]|$1|27|3|28|5|Z|7|4Y|8|@]|9|@]|C|$10|11]]|$1|29|3|2A|5|6|7|4Z|8|@$A|50|B|51|18|19]]|9|@]|C|$]]|$1|2B|3|-4|5|6|7|52|8|@]|9|@]|C|$]]|$1|2C|3|2D|5|6|7|53|8|@]|9|@]|C|$]]|$1|2E|3|2F|5|6|7|54|8|@]|9|@]|C|$]]|$1|2G|3|N|5|O|7|55|8|@]|9|@]|C|$]]|$1|2H|3|2I|5|O|7|56|8|@]|9|@]|C|$]]|$1|2J|3|-4|5|O|7|57|8|@]|9|@]|C|$]]|$1|2K|3|-4|5|6|7|58|8|@]|9|@]|C|$]]|$1|2L|3|-4|5|6|7|59|8|@]|9|@]|C|$]]|$1|2M|3|2N|5|Z|7|5A|8|@]|9|@]|C|$10|11]]|$1|2O|3|-4|5|6|7|5B|8|@]|9|@]|C|$]]|$1|2P|3|2Q|5|6|7|5C|8|@]|9|@]|C|$]]|$1|2R|3|-4|5|6|7|5D|8|@]|9|@]|C|$]]|$1|2S|3|N|5|O|7|5E|8|@]|9|@]|C|$]]|$1|2T|3|2U|5|O|7|5F|8|@]|9|@]|C|$]]|$1|2V|3|2W|5|O|7|5G|8|@]|9|@]|C|$]]|$1|2X|3|-4|5|6|7|5H|8|@]|9|@]|C|$]]|$1|2Y|3|-4|5|6|7|5I|8|@]|9|@]|C|$]]|$1|2Z|3|30|5|Z|7|5J|8|@]|9|@]|C|$10|11]]|$1|31|3|32|5|6|7|5K|8|@$A|5L|B|5M|18|19]]|9|@]|C|$]]|$1|33|3|-4|5|6|7|5N|8|@]|9|@]|C|$]]]|34|$35|$5|36|37|38|C|$39|3A]]|3B|$5|36|37|38|C|$39|3C]]]]

See <a href="https://github.com/jinahya/executable-jar-with-maven-example" rel="noreferrer">executable-jar-with-maven-example</a> (GitHub)
<h2>Notes</h2>
Those pros and cons are provided by <a href="https://stackoverflow.com/users/363573/stephan">Stephan</a>.
<hr />
<h2>For Manual Deployment</h2>
<ul>
<li>Pros</li>
<li>Cons
<ul>
<li>Dependencies are out of the final jar.</li>
</ul>
</li>
</ul>
<h3>Copy Dependencies to a specific directory</h3>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-dependencies&lt;/id&gt;
 &lt;phase&gt;prepare-package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;${project.build.directory}/${project.build.finalName}.lib&lt;/outputDirectory&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
<h3>Make the Jar Executable and Classpath Aware</h3>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;classpathPrefix&gt;${project.build.finalName}.lib/&lt;/classpathPrefix&gt;
 &lt;mainClass&gt;${fully.qualified.main.class}&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
&lt;/plugin&gt;
</code></pre>
At this point the <code>jar</code> is actually executable with external classpath elements.
<pre><code>$ java -jar target/${project.build.finalName}.jar
</code></pre>
<h3>Make Deployable Archives</h3>
The <code>jar</code> file is only executable with the sibling <code>...lib/</code> directory. We need to make archives to deploy with the directory and its content.
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-antrun-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;antrun-archive&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;run&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;target&gt;
 &lt;property name=&quot;final.name&quot; value=&quot;${project.build.directory}/${project.build.finalName}&quot;/&gt;
 &lt;property name=&quot;archive.includes&quot; value=&quot;${project.build.finalName}.${project.packaging} ${project.build.finalName}.lib/*&quot;/&gt;
 &lt;property name=&quot;tar.destfile&quot; value=&quot;${final.name}.tar&quot;/&gt;
 &lt;zip basedir=&quot;${project.build.directory}&quot; destfile=&quot;${final.name}.zip&quot; includes=&quot;${archive.includes}&quot; /&gt;
 &lt;tar basedir=&quot;${project.build.directory}&quot; destfile=&quot;${tar.destfile}&quot; includes=&quot;${archive.includes}&quot; /&gt;
 &lt;gzip src=&quot;${tar.destfile}&quot; destfile=&quot;${tar.destfile}.gz&quot; /&gt;
 &lt;bzip2 src=&quot;${tar.destfile}&quot; destfile=&quot;${tar.destfile}.bz2&quot; /&gt;
 &lt;/target&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
Now you have <code>target/${project.build.finalName}.(zip|tar|tar.bz2|tar.gz)</code> which each contains the <code>jar</code> and <code>lib/*</code>.
<hr />
<h2>Apache Maven Assembly Plugin</h2>
<ul>
<li>Pros</li>
<li>Cons
<ul>
<li>No class relocation support (use maven-shade-plugin if class relocation is needed).</li>
</ul>
</li>
</ul>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;${fully.qualified.main.class}&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
You have <code>target/${project.bulid.finalName}-jar-with-dependencies.jar</code>.
<hr />
<h2>Apache Maven Shade Plugin</h2>
<ul>
<li>Pros</li>
<li>Cons</li>
</ul>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-shade-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;shade&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;shadedArtifactAttached&gt;true&lt;/shadedArtifactAttached&gt;
 &lt;transformers&gt;
 &lt;transformer implementation=&quot;org.apache.maven.plugins.shade.resource.ManifestResourceTransformer&quot;&gt;
 &lt;mainClass&gt;${fully.qualified.main.class}&lt;/mainClass&gt;
 &lt;/transformer&gt;
 &lt;/transformers&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
You have <code>target/${project.build.finalName}-shaded.jar</code>.
<hr />
<h2>onejar-maven-plugin</h2>
<ul>
<li>Pros</li>
<li>Cons
<ul>
<li>Not actively supported since 2012.</li>
</ul>
</li>
</ul>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;!--groupId&gt;org.dstovall&lt;/groupId--&gt; &lt;!-- not available on the central --&gt;
 &lt;groupId&gt;com.jolira&lt;/groupId&gt;
 &lt;artifactId&gt;onejar-maven-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;configuration&gt;
 &lt;mainClass&gt;${fully.qualified.main.class}&lt;/mainClass&gt;
 &lt;attachToBuild&gt;true&lt;/attachToBuild&gt;
 &lt;!-- https://code.google.com/p/onejar-maven-plugin/issues/detail?id=8 --&gt;
 &lt;!--classifier&gt;onejar&lt;/classifier--&gt;
 &lt;filename&gt;${project.build.finalName}-onejar.${project.packaging}&lt;/filename&gt;
 &lt;/configuration&gt;
 &lt;goals&gt;
 &lt;goal&gt;one-jar&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
<hr />
<h2>Spring Boot Maven Plugin</h2>
<ul>
<li>Pros</li>
<li>Cons
<ul>
<li>Add potential unecessary Spring and Spring Boot related classes.</li>
</ul>
</li>
</ul>
<pre class="lang-xml prettyprint-override"><code>&lt;plugin&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;repackage&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;classifier&gt;spring-boot&lt;/classifier&gt;
 &lt;mainClass&gt;${fully.qualified.main.class}&lt;/mainClass&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>
You have <code>target/${project.bulid.finalName}-spring-boot.jar</code>.

blocks|key|371700|text|我在这里尝试了投票最多的答案，并能够使jar可运行。但是程序没有正确运行。我不知道原因是什么。当我尝试从Eclipse运行时，我得到了不同的结果，但是当我从命令行运行jar时，我得到了不同的结果(它崩溃了，并出现了特定于程序的运行时错误)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|371701|我有一个与OP类似的需求，只是我的项目有太多(Maven)依赖项。幸运的是，对我来说唯一有效的解决方案是使用Eclipse。非常简单和直接。这不是OP的解决方案，而是为有类似需求但有许多Maven依赖项的人提供的解决方案，|371702|1)只需右键单击您的项目文件夹(在Eclipse中)并选择Export|371703|2)然后选择Java+->+Runnable+Jar|371704|3)系统将要求您选择jar文件的位置|371705|4)最后，选择包含要运行的Main方法的类，然后选择Package+dependencies+with+the+Jar+file并单击Finish|371706|entityMap^0|1G|7|0|1I|7|0|T|6|0|6|4|E|C|0|0|Q|12|1V|6|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|L|3|M|5|6|7|15|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]]|D|@]|E|$]]|$1|P|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|Q|$]]

I tried the most up-voted answer here, and was able to get the jar runnable. But the program didn't run correctly. I do not know what the reason was. When I try to run from <code>Eclipse</code>, I get a different result but when I run the jar from command-line I get a different result (it crashes with a program-specific runtime error).

I had a similar requirement as the OP just that I had too many (Maven) dependencies for my project. Fortunately, the only solution that worked for me was that using <code>Eclipse</code>. Very simple and very straightforward. This is not a solution to the OP but is a solution for someone who has a similar requirement but with many Maven dependencies,

1) Just right-click on your project folder (in Eclipse) and select <code>Export</code>

2) Then select <code>Java</code> -> <code>Runnable Jar</code>

3) You will be asked to choose the location of the jar file

4) Finally, select the class that has the Main method that you want to run and choose <code>Package dependencies with the Jar file</code> and click <code>Finish</code>

blocks|key|1048795|text|好的，这就是我的解决方案。我知道它没有使用pom.xml文件。但我在Netbeans上编译和运行我的程序时遇到了问题，但当我尝试Java+-jar+MyJarFile.jar时，它失败了。现在，我不完全理解Maven，我想这就是为什么让Netbeans+8.0.2在库中包含我的jar文件以将它们放入jar文件时遇到问题的原因。我在想如何在Eclipse中使用不带Maven的jar文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1048796|Maven可以编译所有的依赖项和插件。而不是Netbeans。(如果您可以获得Netbeans，并且能够使用java+.jar来完成此操作，请告诉我(%5E.%5E)v是如何实现的)|1048797|已解决-对于Linux，只需打开终端即可。|1048798|然后|1048799|cd+/MyRootDirectoryForMyProject|code-block|syntax|javascript|1048800|下一步|1048801|mvn+org.apache.maven.plugins:maven-compiler-plugin:compile|1048802|1048803|mvn+install|1048804|这将在目标目录中创建jar文件。|1048805|MyJarFile-1.0-jar-with-dependencies.jar|1048806|现在|1048807|cd+target|1048808|(您可能需要运行：chmod+%2Bx+MyJarFile-1.0-jar-with-dependencies.jar)|offset|length|style|CODE|1048809|最后|1048810|java+-jar+MyJarFile-1.0-jar-with-dependencies.jar|1048811|请参阅|1048812|https://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException|1048813|我会在其他几个有类似问题的页面上发布这个解决方案。希望我能把一个人从一周的挫折中解救出来。|1048814|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|0|0|0|0|0|9|1C|0|0|0|0|0|29|0|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1R|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|1S|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|1T|8|@]|9|@]|A|$]]|$1|O|3|P|5|J|7|1U|8|@]|9|@]|A|$K|L]]|$1|Q|3|N|5|6|7|1V|8|@]|9|@]|A|$]]|$1|R|3|S|5|J|7|1W|8|@]|9|@]|A|$K|L]]|$1|T|3|U|5|6|7|1X|8|@]|9|@]|A|$]]|$1|V|3|W|5|J|7|1Y|8|@]|9|@]|A|$K|L]]|$1|X|3|Y|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|Z|3|10|5|J|7|20|8|@]|9|@]|A|$K|L]]|$1|11|3|12|5|6|7|21|8|@$13|22|14|23|15|16]]|9|@]|A|$]]|$1|17|3|18|5|6|7|24|8|@]|9|@]|A|$]]|$1|19|3|1A|5|J|7|25|8|@]|9|@]|A|$K|L]]|$1|1B|3|1C|5|6|7|26|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|6|7|27|8|@]|9|@$13|28|14|29|1|2A]]|A|$]]|$1|1F|3|1G|5|6|7|2B|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|2C|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1E]]]]

Okay, so this is my solution. I know it's not using the pom.xml file. But I had the problem my programmme compiling and running on Netbeans but it failing when I tried Java -jar MyJarFile.jar. Now, I don't fully understand Maven and I think this why was having trouble getting Netbeans 8.0.2 to include my jar file in a library to put them into a jar file. I was thinking about how I used to use jar files with no Maven in Eclipse. 

It's Maven that can compile all the dependanices and plugins. Not Netbeans. (If you can get Netbeans and be able to use java .jar to do this please tell me how (^.^)v )

[Solved - for Linux] by opening a terminal. 

Then

<pre><code>cd /MyRootDirectoryForMyProject
</code></pre>

Next

<pre><code>mvn org.apache.maven.plugins:maven-compiler-plugin:compile
</code></pre>

Next

<pre><code>mvn install
</code></pre>

This will create jar file in the target directory.

<pre><code>MyJarFile-1.0-jar-with-dependencies.jar
</code></pre>

Now

<pre><code>cd target
</code></pre>

(You may need to run: <code>chmod +x MyJarFile-1.0-jar-with-dependencies.jar</code>)

And finally

<pre><code>java -jar MyJarFile-1.0-jar-with-dependencies.jar
</code></pre>

Please see 

<a href="https://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException" rel="nofollow">https://cwiki.apache.org/confluence/display/MAVEN/LifecyclePhaseNotFoundException</a>

I'll post this solution in on a couple of other pages with a similar problem. Hopefully I can save somebody from a week of frustration.

blocks|key|371776|text|这是我发现的最好的方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|371777|++<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-jar-plugin</artifactId>
++++<version>2.4</version>
++++<configuration>
++++++<archive>
++++++++<manifest>
++++++++<addClasspath>true</addClasspath>
++++++++<mainClass>com.myDomain.etc.MainClassName</mainClass>
++++++++<classpathPrefix>dependency-jars/</classpathPrefix>
++++++++</manifest>
++++++</archive>
++++</configuration>
++</plugin>
++<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-dependency-plugin</artifactId>
++++<version>2.5.1</version>
++++<executions>
++++++<execution>
++++++++<id>copy-dependencies</id>
++++++++<phase>package</phase>
++++++++<goals>
++++++++++++<goal>copy-dependencies</goal>
++++++++</goals>
++++++++<configuration>
++++++++++++<outputDirectory>
+++++++++++++++${project.build.directory}/dependency-jars/
++++++++++++</outputDirectory>
++++++++</configuration>
++++++</execution>
++++</executions>
++</plugin>|code-block|syntax|javascript|371778|使用此配置，所有依赖项都将位于/dependency-jars中。我的应用程序没有Main类，只有上下文类，但是我的一个依赖项有一个Main类(com.myDomain.etc.MainClassName)，它启动JMX服务器并接收start或stop参数。因此，我可以像这样启动我的应用程序：|offset|length|style|CODE|371779|java+-jar+./lib/TestApp-1.0-SNAPSHOT.jar+start|371780|我等待着它对你们所有人都有用。|371781|entityMap^0|0|0|F|G|15|4|1U|4|20|U|38|5|3E|4|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]|$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$]]

This is the best way i found:

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.4&lt;/version&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;com.myDomain.etc.MainClassName&lt;/mainClass&gt;
 &lt;classpathPrefix&gt;dependency-jars/&lt;/classpathPrefix&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.5.1&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;
 ${project.build.directory}/dependency-jars/
 &lt;/outputDirectory&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

With this configuration, all dependencies will be located in <code>/dependency-jars</code>. My application has no <code>Main</code> class, just context ones, but one of my dependencies do have a <code>Main</code> class (<code>com.myDomain.etc.MainClassName</code>) that starts the JMX server, and receives a <code>start</code> or a <code>stop</code> parameter. So with this i was able to start my application like this:

<pre><code>java -jar ./lib/TestApp-1.0-SNAPSHOT.jar start
</code></pre>

I wait it be useful for you all.

blocks|key|4436350|text|这篇博客文章展示了另一种组合maven-jar和maven-assembly插件的方法。使用博客文章中的程序集配置xml，还可以控制是否将展开依赖项，或者只是将依赖项收集到文件夹中并由清单中的类路径条目引用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436351|4436352|理想的解决方案是将jar包含在lib文件夹中，主jar的manifest.mf文件包含类路径中的所有jar。|blockquote|4436353|4436354|4436355|这里描述的就是这个：https://caffebig.wordpress.com/2013/04/05/executable-jar-file-with-dependent-jars-using-maven/|offset|length|4436356|entityMap|0|LINK|mutability|MUTABLE|url|https://caffebig.wordpress.com/2013/04/05/executable-jar-file-with-dependent-jars-using-maven/^0|0|0|0|0|0|A|2M|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|U|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|V|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|W|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@]|9|@$J|Z|K|10|1|11]]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

This blog post shows another approach with combining the maven-jar and maven-assembly plugins. With the assembly configuration xml from the blog post it can also be controlled if dependencies will be expanded or just be collected in a folder and referenced by a classpath entry in the manifest:

<blockquote>
 The ideal solution is to include the jars in a lib folder and the manifest.mf file of the main jar include all the jars in classpath.
</blockquote>

And exactly that one is described here: <a href="https://caffebig.wordpress.com/2013/04/05/executable-jar-file-with-dependent-jars-using-maven/" rel="nofollow">https://caffebig.wordpress.com/2013/04/05/executable-jar-file-with-dependent-jars-using-maven/</a>

blocks|key|1053671|text|我检查了每一个响应，希望生成一个包含所有依赖项的胖的可执行jar，但没有一个运行正常。答案是阴影插件，它非常简单和直接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1053672|++++<plugin>
++++++<groupId>org.apache.maven.plugins</groupId>
++++++<artifactId>maven-shade-plugin</artifactId>
++++++<version>2.3</version>
++++++<executions>
+++++++++
++++++++<execution>
++++++++<phase>package</phase>
++++++++<goals>
++++++++++++<goal>shade</goal>
++++++++</goals>
++++++++<configuration>
++++++++++<transformers>
+++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
++++++++++++++++<mainClass>path.to.MainClass</mainClass>
+++++++++++++</transformer>
++++++++++</transformers>
++++++++</configuration>
++++++++++</execution>
++++++</executions>
++++</plugin>|code-block|syntax|javascript|1053673|请注意，您的依赖项需要有编译或运行时的作用域，才能正常工作。|1053674|This+example+came+from+mkyong.com|offset|length|1053675|entityMap|0|LINK|mutability|MUTABLE|url|http://www.mkyong.com/maven/create-a-fat-jar-file-maven-shade-plugin/^0|0|0|0|0|X|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I went through every one of these responses looking to make a fat executable jar containing all dependencies and none of them worked right. The answer is the shade plugin, its very easy and straightforward.

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-shade-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.3&lt;/version&gt;
 &lt;executions&gt;
 &lt;!-- Run shade goal on package phase --&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;shade&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;transformers&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"&gt;
 &lt;mainClass&gt;path.to.MainClass&lt;/mainClass&gt;
 &lt;/transformer&gt;
 &lt;/transformers&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

Be aware that your dependencies need to have a scope of compile or runtime for this to work properly.

<a href="http://www.mkyong.com/maven/create-a-fat-jar-file-maven-shade-plugin/" rel="noreferrer">This example came from mkyong.com</a>

blocks|key|3589668|text|这也可以是一个选项，您将能够构建您的jar文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589669|<build>
++++<plugins>
++++++++<plugin>
++++++++++++
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-jar-plugin</artifactId>
++++++++++++<version>2.4</version>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++<classpathPrefix>lib/</classpathPrefix>
++++++++++++++++++++++++<mainClass>WordListDriver</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++</configuration>
++++++++</plugin>
++++</plugins>
</build>|code-block|syntax|javascript|3589670|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This could also be an option,You will be able to build your jar file

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;!-- Build an executable JAR --&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-jar-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.4&lt;/version&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;classpathPrefix&gt;lib/&lt;/classpathPrefix&gt;
 &lt;mainClass&gt;WordListDriver&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

blocks|key|4436467|text|我比较了这篇文章中提到的树插件。我生成了2个jars和一个包含所有jars的目录。我比较了一下结果，maven-shade-plugin绝对是最好的。我面临的挑战是，我有多个spring资源需要合并，还有jax-rs和JDBC服务。与maven-assembly-plugin相比，它们都被shade插件正确地合并了。在这种情况下，除非您将它们复制到您自己的资源文件夹中并手动合并一次，否则spring将失败。这两个插件都会输出正确的依赖树。我有多个作用域，比如test、provide、compile等，两个插件都跳过了测试和提供的范围。他们都产生了相同的清单，但我能够使用他们的转换器将许可证与shade插件合并。使用maven-dependency-plugin，您当然不会有这些问题，因为jars没有被提取出来。但就像其他人指出的那样，你需要携带一个额外的文件才能正常工作。这是pom.xml的一个片段|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436468|++++++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-dependency-plugin</artifactId>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>copy-dependencies</id>
++++++++++++++++++++<phase>prepare-package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>copy-dependencies</goal>
++++++++++++++++++++</goals>
++++++++++++++++++++<configuration>
++++++++++++++++++++++++<outputDirectory>${project.build.directory}/lib</outputDirectory>
++++++++++++++++++++++++<includeScope>compile</includeScope>
++++++++++++++++++++++++<excludeTransitive>true</excludeTransitive>
++++++++++++++++++++++++<overWriteReleases>false</overWriteReleases>
++++++++++++++++++++++++<overWriteSnapshots>false</overWriteSnapshots>
++++++++++++++++++++++++<overWriteIfNewer>true</overWriteIfNewer>
++++++++++++++++++++</configuration>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<version>2.6</version>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++<mainClass>com.rbccm.itf.cdd.poller.landingzone.LandingZonePoller</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++++++<descriptorRefs>
++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++</descriptorRefs>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>make-my-jar-with-dependencies</id>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-shade-plugin</artifactId>
++++++++++++<version>2.4.3</version>
++++++++++++<configuration>
++++++++++++++++<shadedArtifactAttached>false</shadedArtifactAttached>
++++++++++++++++<keepDependenciesWithProvidedScope>false</keepDependenciesWithProvidedScope>
++++++++++++++++<transformers>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++<resource>META-INF/services/javax.ws.rs.ext.Providers</resource>
++++++++++++++++++++</transformer>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++<resource>META-INF/spring.factories</resource>
++++++++++++++++++++</transformer>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++<resource>META-INF/spring.handlers</resource>
++++++++++++++++++++</transformer>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++<resource>META-INF/spring.schemas</resource>
++++++++++++++++++++</transformer>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer">
++++++++++++++++++++++++<resource>META-INF/spring.tooling</resource>
++++++++++++++++++++</transformer>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"/>
++++++++++++++++++++<transformer+implementation="org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer">
++++++++++++++++++++</transformer>
++++++++++++++++</transformers>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>shade</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>|code-block|syntax|javascript|4436469|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I compared the tree plugins mentioned in this post. I generated 2 jars and a directory with all the jars. I compared the results and definitely the maven-shade-plugin is the best. My challenge was that I have multiple spring resources that needed to be merged, as well as jax-rs, and JDBC services. They were all merged properly by the shade plugin in comparison with the maven-assembly-plugin. In which case the spring will fail unless you copy them to your own resources folder and merge them manually one time. Both plugins output the correct dependency tree. I had multiple scopes like test,provide, compile, etc the test and provided were skipped by both plugins. They both produced the same manifest but I was able to consolidate licenses with the shade plugin using their transformer.
With the maven-dependency-plugin of course you don't have those problems because the jars are not extracted. But like some other have pointed you need to carry one extra file(s) to work properly.
Here is a snip of the pom.xml

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-dependency-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;copy-dependencies&lt;/id&gt;
 &lt;phase&gt;prepare-package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;copy-dependencies&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;configuration&gt;
 &lt;outputDirectory&gt;${project.build.directory}/lib&lt;/outputDirectory&gt;
 &lt;includeScope&gt;compile&lt;/includeScope&gt;
 &lt;excludeTransitive&gt;true&lt;/excludeTransitive&gt;
 &lt;overWriteReleases&gt;false&lt;/overWriteReleases&gt;
 &lt;overWriteSnapshots&gt;false&lt;/overWriteSnapshots&gt;
 &lt;overWriteIfNewer&gt;true&lt;/overWriteIfNewer&gt;
 &lt;/configuration&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.6&lt;/version&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;com.rbccm.itf.cdd.poller.landingzone.LandingZonePoller&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-my-jar-with-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-shade-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.4.3&lt;/version&gt;
 &lt;configuration&gt;
 &lt;shadedArtifactAttached&gt;false&lt;/shadedArtifactAttached&gt;
 &lt;keepDependenciesWithProvidedScope&gt;false&lt;/keepDependenciesWithProvidedScope&gt;
 &lt;transformers&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/services/javax.ws.rs.ext.Providers&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/spring.factories&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/spring.handlers&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/spring.schemas&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.AppendingTransformer"&gt;
 &lt;resource&gt;META-INF/spring.tooling&lt;/resource&gt;
 &lt;/transformer&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.ServicesResourceTransformer"/&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.ManifestResourceTransformer"/&gt;
 &lt;transformer implementation="org.apache.maven.plugins.shade.resource.ApacheLicenseResourceTransformer"&gt;
 &lt;/transformer&gt;
 &lt;/transformers&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;shade&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
</code></pre>

blocks|key|1048932|text|对于任何希望从uber-jar中排除特定依赖项的人来说，这是一个对我有效的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1048933|<project...>
<dependencies>
++++++++<dependency>
++++++++++++<groupId>org.apache.spark</groupId>
++++++++++++<artifactId>spark-core_2.11</artifactId>
++++++++++++<version>1.6.1</version>
++++++++++++<scope>provided</scope>+<=============
++++++++</dependency>
</dependencies>
<build>
++++++++<plugins>
++++++++++++<plugin>
++++++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++++++<configuration>
++++++++++++++++++++<descriptorRefs>
++++++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++++++</descriptorRefs>
++++++++++++++++++++<archive>
++++++++++++++++++++++++<manifest>
++++++++++++++++++++++++++++<mainClass>...</mainClass>
++++++++++++++++++++++++</manifest>
++++++++++++++++++++</archive>
++++++++++++++++</configuration>
++++++++++++++++<executions>
++++++++++++++++++++<execution>
++++++++++++++++++++++++<id>make-assembly</id>
++++++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++++++<goals>
++++++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++++++</goals>
++++++++++++++++++++</execution>
++++++++++++++++</executions>
++++++++++++</plugin>
++++++++</plugins>
++++</build>
</project>|code-block|syntax|javascript|1048934|因此，它不是mvn-assembly-plugin的配置，而是依赖项的属性。|1048935|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For anyone looking for options to exclude specific dependencies from the uber-jar, this is a solution that worked for me:

<pre><code>&lt;project...&gt;
&lt;dependencies&gt;
 &lt;dependency&gt;
 &lt;groupId&gt;org.apache.spark&lt;/groupId&gt;
 &lt;artifactId&gt;spark-core_2.11&lt;/artifactId&gt;
 &lt;version&gt;1.6.1&lt;/version&gt;
 &lt;scope&gt;provided&lt;/scope&gt; &lt;=============
 &lt;/dependency&gt;
&lt;/dependencies&gt;
&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;mainClass&gt;...&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-assembly&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
&lt;/project&gt;
</code></pre>

So it's not a configuration of the mvn-assembly-plugin but a property of the dependency.

blocks|key|3589807|text|为了解决这个问题，我们将使用Maven+Assembly插件，它将JAR连同它的依赖JAR一起创建到一个可执行的JAR文件中。只需在pom.xml文件中添加以下插件配置即可。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3589808|<build>
+++<pluginManagement>
++++++<plugins>
+++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<configuration>
+++++++++++++++<archive>
++++++++++++++++++<manifest>
+++++++++++++++++++++<addClasspath>true</addClasspath>
+++++++++++++++++++++<mainClass>com.your.package.MainClass</mainClass>
++++++++++++++++++</manifest>
+++++++++++++++</archive>
+++++++++++++++<descriptorRefs>
++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
+++++++++++++++</descriptorRefs>
++++++++++++</configuration>
++++++++++++<executions>
+++++++++++++++<execution>
++++++++++++++++++<id>make-my-jar-with-dependencies</id>
++++++++++++++++++<phase>package</phase>
++++++++++++++++++<goals>
+++++++++++++++++++++<goal>single</goal>
++++++++++++++++++</goals>
+++++++++++++++</execution>
++++++++++++</executions>
+++++++++</plugin>
++++++</plugins>
+++</pluginManagement>
</build>|code-block|syntax|javascript|3589809|完成此操作后，不要忘记使用以下命令运行MAVEN工具:+mvn+clean+compile+assembly:single|3589810|http://jkoder.com/maven-creating-a-jar-together-with-its-dependency-jars-into-a-single-executable-jar-file/|offset|length|3589811|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|2Z|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|U|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|V|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|W|8|@]|9|@$K|X|L|Y|1|Z]]|A|$]]|$1|M|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|J]]]]

To resolve this issue we will use Maven Assembly Plugin that will create the JAR together with its dependency JARs into a single executable JAR file. Just add below plugin configuration in your pom.xml file.

<pre><code>&lt;build&gt;
 &lt;pluginManagement&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;com.your.package.MainClass&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-my-jar-with-dependencies&lt;/id&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/pluginManagement&gt;
&lt;/build&gt;
</code></pre>

After doing this don’t forget to run MAVEN tool with this command mvn clean compile assembly:single

<a href="http://jkoder.com/maven-creating-a-jar-together-with-its-dependency-jars-into-a-single-executable-jar-file/" rel="noreferrer">http://jkoder.com/maven-creating-a-jar-together-with-its-dependency-jars-into-a-single-executable-jar-file/</a>

blocks|key|4436615|text|已经有数以百万计的答案了，我想补充一句，如果你不需要将<mainClass>添加到你的应用程序中，你就不需要entryPoint。例如，可能不一定有+main+方法。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|4436616|maven插件配置|4436617|++<build>
++++<finalName>log-enrichment</finalName>
++++<plugins>
++++++<plugin>
++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++<configuration>
++++++++++<descriptorRefs>
++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++</descriptorRefs>
++++++++</configuration>
++++++</plugin>
++++</plugins>
++</build>|code-block|syntax|javascript|4436618|构建|4436619|mvn+clean+compile+assembly:single|4436620|验证|4436621|ll+target/
total+35100
drwxrwx---+1+root+vboxsf+++++4096+Sep+29+16:25+./
drwxrwx---+1+root+vboxsf+++++4096+Sep+29+16:25+../
drwxrwx---+1+root+vboxsf++++++++0+Sep+29+16:08+archive-tmp/
drwxrwx---+1+root+vboxsf++++++++0+Sep+29+16:25+classes/
drwxrwx---+1+root+vboxsf++++++++0+Sep+29+16:25+generated-sources/
drwxrwx---+1+root+vboxsf++++++++0+Sep+29+16:25+generated-test-sources/
-rwxrwx---+1+root+vboxsf+35929841+Sep+29+16:10+log-enrichment-jar-with-dependencies.jar*
drwxrwx---+1+root+vboxsf++++++++0+Sep+29+16:08+maven-status/|4436622|entityMap^0|R|B|23|4|1W|6|23|4|28|3|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|D]|$9|14|A|15|B|D]|$9|16|A|17|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|18|8|@]|E|@]|F|$]]|$1|I|3|J|5|K|7|19|8|@]|E|@]|F|$L|M]]|$1|N|3|O|5|6|7|1A|8|@]|E|@]|F|$]]|$1|P|3|Q|5|K|7|1B|8|@]|E|@]|F|$L|M]]|$1|R|3|S|5|6|7|1C|8|@]|E|@]|F|$]]|$1|T|3|U|5|K|7|1D|8|@]|E|@]|F|$L|M]]|$1|V|3|-4|5|6|7|1E|8|@]|E|@]|F|$]]]|W|$]]

There are millions of answers already, I wanted to add you don't need <code>&lt;mainClass&gt;</code> if you don't need to add entryPoint to your application. For example APIs may not have necessarily have <code>main</code> method.

<h2>maven plugin config</h2>

<pre><code> &lt;build&gt;
 &lt;finalName&gt;log-enrichment&lt;/finalName&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
 &lt;/build&gt;
</code></pre>

<h2>build</h2>

<pre><code>mvn clean compile assembly:single
</code></pre>

<h2>verify</h2>

<pre><code>ll target/
total 35100
drwxrwx--- 1 root vboxsf 4096 Sep 29 16:25 ./
drwxrwx--- 1 root vboxsf 4096 Sep 29 16:25 ../
drwxrwx--- 1 root vboxsf 0 Sep 29 16:08 archive-tmp/
drwxrwx--- 1 root vboxsf 0 Sep 29 16:25 classes/
drwxrwx--- 1 root vboxsf 0 Sep 29 16:25 generated-sources/
drwxrwx--- 1 root vboxsf 0 Sep 29 16:25 generated-test-sources/
-rwxrwx--- 1 root vboxsf 35929841 Sep 29 16:10 log-enrichment-jar-with-dependencies.jar*
drwxrwx--- 1 root vboxsf 0 Sep 29 16:08 maven-status/
</code></pre>

blocks|key|372029|text|添加到pom.xml：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|372030|++<dependency>
++++++++++++<groupId>com.jolira</groupId>
++++++++++++<artifactId>onejar-maven-plugin</artifactId>
++++++++++++<version>1.4.4</version>
++</dependency>|code-block|syntax|javascript|372031|和|372032|<plugin>
+++++++<groupId>com.jolira</groupId>
+++++++<artifactId>onejar-maven-plugin</artifactId>
+++++++<version>1.4.4</version>
+++++++<executions>
++++++++++++++<execution>
+++++++++++++++++++++<goals>
+++++++++++++++++++++++++<goal>one-jar</goal>
+++++++++++++++++++++</goals>
++++++++++++++</execution>
+++++++</executions>
</plugin>|372033|就是这样。下一个mvn包还将额外创建一个fat+jar，包括所有依赖jar。|372034|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Add to pom.xml:

<pre><code> &lt;dependency&gt;
 &lt;groupId&gt;com.jolira&lt;/groupId&gt;
 &lt;artifactId&gt;onejar-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.4.4&lt;/version&gt;
 &lt;/dependency&gt;
</code></pre>

and

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;com.jolira&lt;/groupId&gt;
 &lt;artifactId&gt;onejar-maven-plugin&lt;/artifactId&gt;
 &lt;version&gt;1.4.4&lt;/version&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;one-jar&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

Thats it. Next mvn package will also create one fat jar additionally, including all dependency jars.

blocks|key|4436709|text|您可以使用maven-shade插件构建一个超级jar，如下所示|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4436710|<plugin>
++++<groupId>org.apache.maven.plugins</groupId>
++++<artifactId>maven-shade-plugin</artifactId>
++++<executions>
++++++++<execution>
++++++++++++<phase>package</phase>
++++++++++++<goals>
++++++++++++++++<goal>shade</goal>
++++++++++++</goals>
++++++++</execution>
++++</executions>
</plugin>|code-block|syntax|javascript|4436711|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

You can use maven-shade plugin to build a uber jar like below

<pre><code>&lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-shade-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;shade&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
&lt;/plugin&gt;
</code></pre>

blocks|key|4436719|text|<build>
++++<plugins>
++++++++<plugin>
++++++++++++<groupId>org.apache.maven.plugins</groupId>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<version>2.4.1</version>
++++++++++++<configuration>
++++++++++++++++
++++++++++++++++<descriptorRefs>
++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++</descriptorRefs>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<id>make-assembly</id>
++++++++++++++++++++
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++</plugins>
</build>|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4436720|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>&lt;build&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;version&gt;2.4.1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;!-- get all project dependencies --&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;id&gt;make-assembly&lt;/id&gt;
 &lt;!-- bind to the packaging phase --&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;
</code></pre>

blocks|key|372094|text|我希望我的经验可以帮助某些人:我想将我的应用程序Spring+(使用cas客户端)迁移到Spring+Boot+(1.5版而不是2.4版)。我遇到了很多问题，比如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|372095|在|372096|+/cas-client-web.jar中没有主清单属性|blockquote|372097|372098|372099|我想创建一个包含所有依赖项的唯一jar。在网上搜索了几天之后。我可以使用以下几行代码完成我的工作：|372100|+++++++++<plugin>
++++++++++++<groupId>org.springframework.boot</groupId>
++++++++++++<artifactId>spring-boot-maven-plugin</artifactId>
++++++++++++<configuration>
++++++++++++++++<fork>true</fork>
++++++++++++++++<mainClass>${start-class}</mainClass>
++++++++++++</configuration>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>repackage</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++</plugin>
++++++++<plugin>
++++++++++++<artifactId>maven-assembly-plugin</artifactId>
++++++++++++<executions>
++++++++++++++++<execution>
++++++++++++++++++++<phase>package</phase>
++++++++++++++++++++<goals>
++++++++++++++++++++++++<goal>single</goal>
++++++++++++++++++++</goals>
++++++++++++++++</execution>
++++++++++++</executions>
++++++++++++<configuration>
++++++++++++++++<archive>
++++++++++++++++++++<manifest>
++++++++++++++++++++++++<addClasspath>true</addClasspath>
++++++++++++++++++++++++<mainClass>${start-class}</mainClass>
++++++++++++++++++++</manifest>
++++++++++++++++</archive>
++++++++++++++++<descriptorRefs>
++++++++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++++++</descriptorRefs>
++++++++++++</configuration>
++++++++</plugin>|code-block|syntax|javascript|372101|使用start-class是您的主类|372102|<properties>
++++<java.version>1.8</java.version>
++++<start-class>com.test.Application</start-class>
</properties>|372103|我的应用程序如下：|372104|package+com.test;

import+java.util.Arrays;

import+com.test.TestProperties;
import+org.springframework.boot.CommandLineRunner;
import+org.springframework.boot.SpringApplication;
import+org.springframework.boot.autoconfigure.EnableAutoConfiguration;
import+org.springframework.boot.autoconfigure.SpringBootApplication;
import+org.springframework.boot.context.properties.EnableConfigurationProperties;
import+org.springframework.context.ApplicationContext;
import+org.springframework.context.annotation.Bean;


@SpringBootApplication
@EnableAutoConfiguration
@EnableConfigurationProperties({TestProperties.class})
public+class+Application+{

public+static+void+main(String[]+args)+{
++++SpringApplication.run(Application.class,+args);
}

@Bean
public+CommandLineRunner+commandLineRunner(ApplicationContext+ctx)+{
++++return+args+->+{

++++++++System.out.println("Let's+inspect+the+beans+provided+by+Spring+Boot:");

++++++++String[]+beanNames+=+ctx.getBeanDefinitionNames();
++++++++Arrays.sort(beanNames);
++++++++for+(String+beanName+:+beanNames)+{
++++++++++++System.out.println(beanName);
++++++++}

++++};
}

}|372105|entityMap^0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@]|A|$]]|$1|G|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|15|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|16|8|@]|9|@]|A|$]]|$1|R|3|S|5|M|7|17|8|@]|9|@]|A|$N|O]]|$1|T|3|U|5|6|7|18|8|@]|9|@]|A|$]]|$1|V|3|W|5|M|7|19|8|@]|9|@]|A|$N|O]]|$1|X|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|Y|$]]

I hope my experience can help somebody: I want to migrate my app Spring (using cas client) to Spring Boot (1.5 not 2.4 yet). I stucked with many problem like :
<blockquote>
no main manifest attribute, in target/cas-client-web.jar
</blockquote>
I want to make one unique jar with all dependencies. After some days in searching on the Internet. I can do my job with theses lines :
<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;
 &lt;artifactId&gt;spring-boot-maven-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;fork&gt;true&lt;/fork&gt;
 &lt;mainClass&gt;${start-class}&lt;/mainClass&gt;
 &lt;/configuration&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;goals&gt;
 &lt;goal&gt;repackage&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;executions&gt;
 &lt;execution&gt;
 &lt;phase&gt;package&lt;/phase&gt;
 &lt;goals&gt;
 &lt;goal&gt;single&lt;/goal&gt;
 &lt;/goals&gt;
 &lt;/execution&gt;
 &lt;/executions&gt;
 &lt;configuration&gt;
 &lt;archive&gt;
 &lt;manifest&gt;
 &lt;addClasspath&gt;true&lt;/addClasspath&gt;
 &lt;mainClass&gt;${start-class}&lt;/mainClass&gt;
 &lt;/manifest&gt;
 &lt;/archive&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>
with start-class is your main class
<pre><code>&lt;properties&gt;
 &lt;java.version&gt;1.8&lt;/java.version&gt;
 &lt;start-class&gt;com.test.Application&lt;/start-class&gt;
&lt;/properties&gt;
</code></pre>
And my Application is like :
<pre><code>package com.test;

import java.util.Arrays;

import com.test.TestProperties;
import org.springframework.boot.CommandLineRunner;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.EnableAutoConfiguration;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.boot.context.properties.EnableConfigurationProperties;
import org.springframework.context.ApplicationContext;
import org.springframework.context.annotation.Bean;


@SpringBootApplication
@EnableAutoConfiguration
@EnableConfigurationProperties({TestProperties.class})
public class Application {

public static void main(String[] args) {
 SpringApplication.run(Application.class, args);
}

@Bean
public CommandLineRunner commandLineRunner(ApplicationContext ctx) {
 return args -&gt; {

 System.out.println(&quot;Let's inspect the beans provided by Spring Boot:&quot;);

 String[] beanNames = ctx.getBeanDefinitionNames();
 Arrays.sort(beanNames);
 for (String beanName : beanNames) {
 System.out.println(beanName);
 }

 };
}

}
</code></pre>

blocks|key|372145|text|尝试了多个解决方案，但在我们想要创建一个不可执行的fat+jar的场景中完美工作的一个，其中外部系统的所有内部依赖项都没有以前的相关性。已测试生产方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|372146|将此内容包含在pom.xml中|372147|<?xml+version="1.0"+encoding="UTF-8"?>
<build>
+++<sourceDirectory>src</sourceDirectory>
+++<plugins>
++++++<plugin>
+++++++++<artifactId>maven-compiler-plugin</artifactId>
+++++++++<version>3.8.1</version>
+++++++++<configuration>
++++++++++++<source>1.8</source>
++++++++++++<target>1.8</target>
+++++++++</configuration>
++++++</plugin>
++++++<plugin>
+++++++++<artifactId>maven-assembly-plugin</artifactId>
+++++++++<configuration>
++++++++++++<descriptorRefs>
+++++++++++++++<descriptorRef>jar-with-dependencies</descriptorRef>
++++++++++++</descriptorRefs>
+++++++++</configuration>
++++++</plugin>
+++</plugins>
</build>|code-block|syntax|javascript|372148|运行命令来构建fat+jar->>+mvn程序集:assembly|372149|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

tried multiple solutions but the one that worked perfectly in the scenario where we wanted to create a non executable fat jar with all internal dependencies for external systems having no previous relevance. prod scenario tested.
include this in the pom.xml
<pre><code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;build&gt;
 &lt;sourceDirectory&gt;src&lt;/sourceDirectory&gt;
 &lt;plugins&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-compiler-plugin&lt;/artifactId&gt;
 &lt;version&gt;3.8.1&lt;/version&gt;
 &lt;configuration&gt;
 &lt;source&gt;1.8&lt;/source&gt;
 &lt;target&gt;1.8&lt;/target&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;plugin&gt;
 &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
 &lt;configuration&gt;
 &lt;descriptorRefs&gt;
 &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;
 &lt;/descriptorRefs&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
 &lt;/plugins&gt;
&lt;/build&gt;


</code></pre>
Command to run to build the fat jar-&gt;&gt; mvn assembly:assembly

I want to package my project in a single executable JAR for distribution.

How can I make a Maven project package all dependency JARs into my output JAR?

How can I create an executable JAR with dependencies using Maven?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想将我的项目打包到一个可执行的JAR中，以便分发。如何使Maven项目将所有依赖JAR打包到我的输出JAR中？

问如何使用Maven创建具有依赖关系的可执行JAR？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何使用Maven创建具有依赖关系的可执行JAR？EN