如果你的项目是war或ear类型，专家会复制依赖项。

你可以使用Shade插件创建一个超级罐子，你可以在里面捆绑你所有的第三方依赖。

你所需要的只是在pom.xml的build/plugins里面的以下代码片段:

<plugin>
    <artifactId>maven-dependency-plugin</artifactId>
    <executions>
        <execution>
            <phase>prepare-package</phase>
            <goals>
                <goal>copy-dependencies</goal>
            </goals>
            <configuration>
                <outputDirectory>${project.build.directory}/lib</outputDirectory>
            </configuration>
        </execution>
    </executions>
</plugin>

当您运行时，上面的代码将在包阶段运行

mvn clean package

依赖项将被复制到代码片段中指定的outputDirectory，在本例中为lib。

如果只是偶尔这样做，则不需要更改pom.xml。简单地运行以下命令:

mvn clean package dependency:copy-dependencies

重写默认位置${project.build。目录}/依赖，添加一个名为outputDirectory的系统属性，即

    -DoutputDirectory=${project.build.directory}/lib

如果您想交付应用程序jar的一个包，以及它的所有依赖项和一些调用MainClass的脚本，请查看appassembler-maven-plugin。

下面的配置将为windows和Linux生成启动应用程序的脚本(生成的路径引用所有依赖项jar，下载所有依赖项(到target/appassembler下面的lib文件夹中)。然后，可以使用组装插件将整个appassembler目录打包到一个zip文件中，该文件将与jar文件一起安装/部署到存储库中。

  <plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>appassembler-maven-plugin</artifactId>
    <version>1.0</version>
    <executions>
      <execution>
        <id>generate-jsw-scripts</id>
        <phase>package</phase>
        <goals>
          <goal>generate-daemons</goal>
        </goals>
        <configuration>
          <!--declare the JSW config -->
          <daemons>
            <daemon>
              <id>myApp</id>
              <mainClass>name.seller.rich.MyMainClass</mainClass>
              <commandLineArguments>
                <commandLineArgument>start</commandLineArgument>
              </commandLineArguments>
              <platforms>
                <platform>jsw</platform>
              </platforms>              
            </daemon>
          </daemons>
          <target>${project.build.directory}/appassembler</target>
        </configuration>
      </execution>
      <execution>
        <id>assemble-standalone</id>
        <phase>integration-test</phase>
        <goals>
          <goal>assemble</goal>
        </goals>
        <configuration>
          <programs>
            <program>
              <mainClass>name.seller.rich.MyMainClass</mainClass>
              <!-- the name of the bat/sh files to be generated -->
              <name>mymain</name>
            </program>
          </programs>
          <platforms>
            <platform>windows</platform>
            <platform>unix</platform>
          </platforms>
          <repositoryLayout>flat</repositoryLayout>
          <repositoryName>lib</repositoryName>
        </configuration>
      </execution>
    </executions>
  </plugin>
  <plugin>
    <artifactId>maven-assembly-plugin</artifactId>
    <version>2.2-beta-4</version>
    <executions>
      <execution>
        <phase>integration-test</phase>
        <goals>
          <goal>single</goal>
        </goals>
        <configuration>
          <descriptors>
            <descriptor>src/main/assembly/archive.xml</descriptor>
          </descriptors>
        </configuration>
      </execution>
    </executions>
  </plugin> 

将目录目录打包为zip文件的程序集描述符(在src/main/assembly中)如下:

<assembly>
  <id>archive</id>
  <formats>
    <format>zip</format>
  </formats>
  <fileSets>
    <fileSet>
     <directory>${project.build.directory}/appassembler</directory>
     <outputDirectory>/</outputDirectory>
    </fileSet>
  </fileSets>
</assembly>

如果您在Eclipse中的Tomcat服务器上运行时遇到与WEB-INF/lib文件中未出现依赖项相关的问题，请查看以下内容:

启动Tomcat时的DispatcherServlet (Maven依赖没有复制到wtpwebapps)

您只需在项目属性>部署程序集中添加Maven依赖项。

最好的方法取决于你想做什么:

If you want to bundle your dependencies into a WAR or EAR file, then simply set the packaging type of your project to EAR or WAR. Maven will bundle the dependencies into the right location. If you want to create a JAR file that includes your code along with all your dependencies, then use the assembly plugin with the jar-with-dependencies descriptor. Maven will generate a complete JAR file with all your classes plus the classes from any dependencies. If you want to simply pull your dependencies into the target directory interactively, then use the dependency plugin to copy your files in. If you want to pull in the dependencies for some other type of processing, then you will probably need to generate your own plugin. There are APIs to get the list of dependencies, and their location on disk. You will have to take it from there...