Maven 打包方式探究

最新推荐文章于 2024-09-27 05:46:25 发布
最新推荐文章于 2024-09-27 05:46:25 发布
阅读量1.2k 收藏 2
点赞数 1
分类专栏： Java 文章标签： maven java jar 打包
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/caozicheng1999/article/details/126263361
版权

Maven 打包方式探究

参考资料：

Maven打包可执行jar包方法大全（史上最全）_AllenLeungX的博客-CSDN博客_maven打包可执行jar包

测试仓库：

代码浏览 - maven-package-demo - Maven-Example - caozicheng (coding.net)

方法零：maven-jar-plugin

什么插件都不添加，就用默认的配置，直接mvn package，从信息来看，maven使用的默认打包插件是maven-jar-plugin

[INFO] Building maven-package-demo 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ maven-package-demo ---
[INFO] Deleting /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ maven-package-demo ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ maven-package-demo ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
[INFO] Compiling 1 source file to /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ maven-package-demo ---
[INFO] Not copying test resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ maven-package-demo ---
[INFO] Not compiling test sources
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @ maven-package-demo ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ maven-package-demo ---
[INFO] Building jar: /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/Test.jar
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  3.518 s
[INFO] Finished at: 2022-08-10T10:51:50+08:00
[INFO] ------------------------------------------------------------------------

这生成出来的，实际上是一个没有指定mainClass，也没有指定classpath的包，关于怎么执行，看“问题二”，当然实际生产时不可能这么做，直接看下面的方法吧。

方法一：使用maven-jar-plugin和maven-dependency-plugin

maven-jar-plugin配合maven-dependency-plugin把所依赖的jar包copy到指定目录

<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-jar-plugin</artifactId>
    <configuration>
        <archive>
            <manifest>
                <!--是否在manifest文件中添加classpath。默认为false。如果为true，则会在manifest文件中添加classpath，这样在启动的时候就不用再手动指定classpath-->
                <addClasspath>true</addClasspath>
                <!--所依赖jar包所在的文件夹-->
                <classpathPrefix>libs/</classpathPrefix>
                <mainClass>
                    com.test.Main
                </mainClass>
            </manifest>
        </archive>
    </configuration>
</plugin>

<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指定了要将所依赖的jar包copy到哪个目录。要与maven-jar-plugin中的classpathPrefix一致。-->
            <outputDirectory>
                ${project.build.directory}/libs
            </outputDirectory>
        </configuration>
    </execution>
</executions>
</plugin>

查看生成jar包中的MANIFEST.MF文件，classpath被指定为libs

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: caozicheng
Class-Path: libs/slf4j-api-1.7.36.jar libs/log4j-slf4j-impl-2.17.2.jar
  libs/log4j-api-2.17.2.jar libs/log4j-core-2.17.2.jar libs/junit-4.12
 .jar libs/hamcrest-core-1.3.jar
Created-By: Apache Maven 3.8.4
Build-Jdk: 1.8.0_202
Main-Class: com.test.Main

最终打包目录结果是，自己写的Class在jar包中，所依赖的jar包在libs目录中:

├── myClass.jar
├── lib
│ ├── dependence1.jar
│ ├── dependence2.jar

image-20220810094040181

优点

  • 有诸多配置项，很自由，每个步骤都可控。
  • 不同项目使用不同版本的依赖，也方便分离管理。

缺点

  • 打成的最终jar包中没有所依赖的jar包。依赖跟自己的代码不在一个jar包中。部署或者移动的时候，要考虑到多个文件，比较麻烦

方法二：使用maven-assembly-plugin (推荐)

作用：将自己项目中的代码和资源（包含了所有依赖包）打成一个jar包。

打包后会在target目录下生成一个xxx-jar-with-dependencies.jar文件，这个文件不但包含了自己项目中的代码和资源，还包含了所有依赖包的内容。所以可以直接通过java -jar来运行。

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-assembly-plugin</artifactId>
  <configuration>
    <archive>
      <manifest>
        <mainClass>com.test.Main</mainClass>
      </manifest>
    </archive>
    <descriptorRefs>
      <descriptorRef>jar-with-dependencies</descriptorRef>
    </descriptorRefs>
  </configuration>
  <!--下面是为了使用 mvn package命令，如果不加则使用mvn assembly-->
  <executions>
    <execution>
      <id>make-assemble</id>
      <phase>package</phase>
      <goals>
        <goal>single</goal>
      </goals>
    </execution>

  </executions>
</plugin>

优点

  • 所有的东西都打到一个jar包中，出问题的可能大大减少。
    缺点

  • 配置项少，包比较大，不自由。

方法三：使用maven-shade-plugin

跟maven-assembly-plugin类似，都可以将所有的东西都打包到一个jar包中。

<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>com.test.Main</mainClass>
                </transformer>
            </transformers>
        </configuration>
        </execution>
    </executions>
</plugin>

优点

  • 功能同maven-assembly-plugin，可配置项更多。

缺点

  • 配置起来太麻烦。

问题一：classpath 和 jar

经常碰到的问题，IDE中运行完全正常，打包出来就一堆问题。

其实就是两个问题指定mainClass和classpath。

以IDEA为例运行，Run中可以看到，IDEA是将在命令中指定了mainClass和classpath，所以，我们想要简单的通过 java -jar xx.jar 就成功运行，自然需要配置得当。

/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/bin/java -javaagent:/Applications/IntelliJ IDEA.app/Contents/lib/idea_rt.jar=55200:/Applications/IntelliJ IDEA.app/Contents/bin -Dfile.encoding=UTF-8 -classpath /Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/deploy.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/cldrdata.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/jaccess.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/nashorn.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/ext/zipfs.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/jfxswt.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.8/Contents/Home/jre/lib/rt.jar:/Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/classes:/Users/caozicheng/.m2/repository/org/slf4j/slf4j-api/1.7.36/slf4j-api-1.7.36.jar:/Users/caozicheng/.m2/repository/org/apache/logging/log4j/log4j-slf4j-impl/2.17.2/log4j-slf4j-impl-2.17.2.jar:/Users/caozicheng/.m2/repository/org/apache/logging/log4j/log4j-api/2.17.2/log4j-api-2.17.2.jar:/Users/caozicheng/.m2/repository/org/apache/logging/log4j/log4j-core/2.17.2/log4j-core-2.17.2.jar:/Users/caozicheng/.m2/repository/junit/junit/4.12/junit-4.12.jar:/Users/caozicheng/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar com.test.Main

不推荐手动设置classpath，会污染整个系统环境，而且在使用了如maven的包管理软件后，classpath也会更复杂。详见 classpath和jar - 廖雪峰的官方网站 (liaoxuefeng.com)

问题二：打包时不指定classpath，怎么才能 work？

首先，maven-jar-plugin的作用是打不含依赖的jar包，可以配置mainClass，（不指定classpath，测试下如何在执行jar包时手动指定classpath）

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-jar-plugin</artifactId>
  <configuration>
    <archive>
      <manifest>
        <mainClass>
          com.test.Main
        </mainClass>
      </manifest>
    </archive>
  </configuration>
</plugin>

这时候直接运行生成的jar包，会找不到依赖所在的路径。

(base) caozicheng@caozichengdeAir maven-package % java -jar target/Test.jar
Exception in thread "main" java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
        at com.test.Main.<clinit>(Main.java:8)
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
        at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
        ... 1 more

看jar包中的MANIFEST.MF文件，确实classpath是空的

Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Built-By: caozicheng
Created-By: Apache Maven 3.8.4
Build-Jdk: 1.8.0_202
Main-Class: com.test.Main

首先尝试了java -classpath lib/*.jar -jar ABCD.jar，但是并不能work，搜索发现如下。

众所周知，如果采用java -classpath，可以允许用户指定其他的Jar包或者class文件的位置。

比如java -classpath lib/*.jar ABC.class

但是如果采用了-jar参数，-classpath的功能就会被屏蔽。java的加载器会旨在指定的jar文件里面寻找需要的类。比如

java -classpath lib/*.jar -jar ABCD.jar，我们的本意是要运行ABCD.jar文件里面的main函数类，而且这个类依赖lib目录下的那些jar文件，着用的结果就会导致类似下面的错误

Exception in thread “main” java.lang.NoClassDefFoundError: org/apache/poi/ss/usermodel/Workbook、

无论你怎么设置classpath，都不会work。

然后尝试，手动更改jar包中的MANIFEST.MF文件

修改已经打好的jar包中的配置文件 https://www.cnblogs.com/qingtian-jlj/p/13265094.html

最后没成功，不瞎折腾了，老老实实用上面的方法。

Error: Invalid or corrupt jarfile target/Test.jar

问题三：配置了多个打包插件会怎么样？

上述方法一、二、三同时使用会如何？build 标签如下

<build>
        <finalName>Test</finalName>

        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-dependency-plugin</artifactId>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-assembly-plugin</artifactId>
            </plugin>

            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-shade-plugin</artifactId>
            </plugin>

        </plugins>

        <pluginManagement>
            <plugins>

                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-jar-plugin</artifactId>
                    <configuration>
                        <archive>
                            <manifest>
                                <!--是否在manifest文件中添加classpath。默认为false。如果为true，则会在manifest文件中添加classpath，这样在启动的时候就不用再手动指定classpath-->
                                <addClasspath>true</addClasspath>
                                <!--所依赖jar包所在的文件夹-->
                                <classpathPrefix>libs/</classpathPrefix>
                                <mainClass>
                                    com.test.Main
                                </mainClass>
                            </manifest>
                        </archive>
                    </configuration>
                </plugin>

                <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指定了要将所依赖的jar包copy到哪个目录。要与maven-jar-plugin中的classpathPrefix一致。-->
                                <outputDirectory>
                                    ${project.build.directory}/libs
                                </outputDirectory>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>

                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-assembly-plugin</artifactId>
                    <configuration>
                        <archive>
                            <manifest>
                                <mainClass>com.test.Main</mainClass>
                            </manifest>
                        </archive>
                        <descriptorRefs>
                            <descriptorRef>jar-with-dependencies</descriptorRef>
                        </descriptorRefs>

                    </configuration>
                    <!--下面是为了使用 mvn package命令，如果不加则使用mvn assembly-->
                    <executions>
                        <execution>
                            <id>make-assemble</id>
                            <phase>package</phase>
                            <goals>
                                <goal>single</goal>
                            </goals>
                        </execution>

                    </executions>
                </plugin>

                <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>com.test.Main</mainClass>
                                    </transformer>
                                </transformers>
                            </configuration>
                        </execution>
                    </executions>
                </plugin>

            </plugins>
        </pluginManagement>
    </build>

首先，从结果来看，各自插件打包名称不同，不会“冲突”，打出来的包都能work

但是会有一些warning，比如maven-shade-plugin打出来的包（大概就是重复引入依赖了）

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/maven-package-demo-1.0-SNAPSHOT-shaded.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/libs/log4j-slf4j-impl-2.17.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]

从打包信息来看：

  • 实测，插件执行的先后顺序，与声明顺序无关，推测应该是根据插件的功能，由maven来决定。
  • 推测，生成jar包的过程，是先在临时文件夹中写入配置，再package成jar包。
  • 虽然是上一个插件的jar包生成出来之后，才会开始执行下一个插件，但是推测临时文件夹并没有删除，而是“继承”了上一个插件的内容去修改，所以第一个插件maven-jar-plugin可以正常执行，而maven-assembly-plugin执行时，会发现文件已存在就skipping（这个skipping显然是插件面对这种情况的应对策略），最后一个maven-shade-plugin写入时明显还进行了写入，出现了warning（所以，maven-shade-plugin打出来的包执行会有warning）
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ maven-package-demo ---
[INFO] Building jar: /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/Test.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assemble) @ maven-package-demo ---
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/slf4j/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/logging/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/maven/org.apache.logging.log4j/ already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/logging/ already added, skipping
[INFO] org/apache/logging/log4j/ already added, skipping
[INFO] META-INF/versions/ already added, skipping
[INFO] META-INF/versions/9/ already added, skipping
[INFO] META-INF/versions/9/org/ already added, skipping
[INFO] META-INF/versions/9/org/apache/ already added, skipping
[INFO] META-INF/versions/9/org/apache/logging/ already added, skipping
[INFO] META-INF/versions/9/org/apache/logging/log4j/ already added, skipping
[INFO] META-INF/services/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/maven/org.apache.logging.log4j/ already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] org/ already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] org/ already added, skipping
[INFO] Building jar: /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/target/Test-jar-with-dependencies.jar
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/slf4j/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/logging/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/maven/org.apache.logging.log4j/ already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] org/ already added, skipping
[INFO] org/apache/ already added, skipping
[INFO] org/apache/logging/ already added, skipping
[INFO] org/apache/logging/log4j/ already added, skipping
[INFO] META-INF/versions/ already added, skipping
[INFO] META-INF/versions/9/ already added, skipping
[INFO] META-INF/versions/9/org/ already added, skipping
[INFO] META-INF/versions/9/org/apache/ already added, skipping
[INFO] META-INF/versions/9/org/apache/logging/ already added, skipping
[INFO] META-INF/versions/9/org/apache/logging/log4j/ already added, skipping
[INFO] META-INF/services/ already added, skipping
[INFO] META-INF/maven/ already added, skipping
[INFO] META-INF/maven/org.apache.logging.log4j/ already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] org/ already added, skipping
[INFO] META-INF/ already added, skipping
[INFO] META-INF/MANIFEST.MF already added, skipping
[INFO] org/ already added, skipping
[INFO] 
[INFO] --- maven-shade-plugin:3.3.0:shade (default) @ maven-package-demo ---
[INFO] Including org.slf4j:slf4j-api:jar:1.7.36 in the shaded jar.
[INFO] Including org.apache.logging.log4j:log4j-slf4j-impl:jar:2.17.2 in the shaded jar.
[INFO] Including org.apache.logging.log4j:log4j-api:jar:2.17.2 in the shaded jar.
[INFO] Including org.apache.logging.log4j:log4j-core:jar:2.17.2 in the shaded jar.
[INFO] Including junit:junit:jar:4.12 in the shaded jar.
[INFO] Including org.hamcrest:hamcrest-core:jar:1.3 in the shaded jar.
[INFO] Dependency-reduced POM written at: /Users/caozicheng/Library/CloudStorage/OneDrive-stu.suda.edu.cn/repository/java/maven-package/dependency-reduced-pom.xml
[WARNING] Test.jar, hamcrest-core-1.3.jar, junit-4.12.jar, log4j-api-2.17.2.jar, log4j-core-2.17.2.jar, log4j-slf4j-impl-2.17.2.jar, slf4j-api-1.7.36.jar define 1 overlapping resource: 
[WARNING]   - META-INF/MANIFEST.MF
[WARNING] log4j-api-2.17.2.jar, log4j-core-2.17.2.jar, log4j-slf4j-impl-2.17.2.jar define 3 overlapping resources: 
[WARNING]   - META-INF/DEPENDENCIES
[WARNING]   - META-INF/LICENSE
[WARNING]   - META-INF/NOTICE
[WARNING] maven-shade-plugin has detected that some class files are
[WARNING] present in two or more JARs. When this happens, only one
[WARNING] single version of the class is copied to the uber jar.
[WARNING] Usually this is not harmful and you can skip these warnings,
[WARNING] otherwise try to manually exclude artifacts based on
[WARNING] mvn dependency:tree -Ddetail=true and the above output.
[WARNING] See https://maven.apache.org/plugins/maven-shade-plugin/
[INFO] Attaching shaded artifact.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  6.218 s
[INFO] Finished at: 2022-08-10T11:08:39+08:00
[INFO] ------------------------------------------------------------------------

问题四：三种项目打包方式——jar，war，pom的区别

<groupId>org.example</groupId>
<artifactId>maven-package-demo</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>jar</packaging>

jar：默认的打包方式，打包成jar用作jar包使用，本文所探讨的内容。

war：打包成war，发布在服务器上，如网站或服务。用户可以通过浏览器直接访问，或者是通过发布服务被别的工程调用，一般配合SpringBoot等框架使用。

pom：用在父级工程或聚合工程中，用来做jar包的版本控制，必须指明这个聚合工程的打包方式为pom，例如leyou,创建12个model分别为，关于多模块打包：代码浏览 - maven-multi-module - Maven-Example - caozicheng (coding.net)

chengzic1999
关注
专栏目录
【问题】【Maven】Linux环境下Maven打包问题 —— 提示找不到子模块
Sheldon74的博客
03-18 977
一次手贱行为，linux环境下maven打包遇子模块名找不到异常问题。注意文件系统命名linux环境下区分大小写。
Maven项目打包时报错：非法字符\ufeff
qq_40903561的博客
11-19 2685
打包方式： cmd命令行-进入项目目录-输入mvn clean -DskipTests package -P dev，是标准的命令行打包方式 报错： 非法字符: ‘\ufeff’ 需要class, interface或enum。 报错的文件是一个公用包里的一个class，是datasource的，文件名是DataSourceContextHolder.class，一开始我还以为是pom文件里的dev这个profile有问题, 在检查了一遍之后，发现还真有问题，修改完成后再次打包，发现还是一样的报错
maven项目打包
06-20
java　maven项目打包
maven打包
weixin_33812433的博客
12-04 175
1. 背景 工程中免不了要通过maven打包。 2. maven三种打包插件 plugin function site maven-jar-plugin maven 默认打包插件，用来创建 project jar maven-shade-plugin 用来打可执行包，executable(fat) jar http://maven.apache...
使用 Maven 的 package 指令打包 Jar 包 如何操作
最新发布
weixin_45428910的博客
09-27 831
使用 Maven 的 package 指令打包 Jar 包 如何操作
maven简单快速打包package
weixin_73638814的博客
02-21 2293
解决：上网搜你需要的类型在当前java版本的import正确导包是什么或者问gpt（因为每个人做的项目不一样，import也不一样），因为新版本可以兼容旧版本，但是旧版本不能识别新版本的依赖。将项目完成后，所有的工程文件采用聚合的方法利用<module>标签全部整合到一个父工程的pom中（若工程只有一个，不用聚合可忽略）成功后，在本工程的target目录下看看工程名字.jar的文件（如果是聚合，则子工程的target下出现.jar文件）编译生成多余的class文件、打包生成的JAR文件以及其他生成的文件。
maven打包jar包
weixin_30651273的博客
07-11 196
环境变量配置 第一步： 配置好maven：关于maven的配置，官网有教程http://maven.apache.org/download.cgi(注意下载-bin.zip结尾的) 1、首先解压从官网下载的maven包到硬盘的某个位置。首先确保配置了jdk，点击查看jdk配置教程 2、设置系统变量Path添加变量值为%M2_HOME%\bin 3、设置系统变量M2_HOM...
IntelliJ IDEA中关于Maven构建复杂的聚合工程的管理和打包问题
诗和远方，任重道远
07-15 2282
项目结构，如下图 一、管理 1.1 父子间依赖问题 Pom 工程引入Module，直接 New Module 即可，在 父类的Pom.xml 会自动加入module基本信息，如下 <modules> <module>initSqlBuild</module> <module>specificationBuild&lt...
Maven依赖中的scope标签属性探究
weixin_45797022的博客
07-22 339
平时在写spring的项目配置pom.xml时，都是直接照着网上别人讲解的代码开始配置，对于scope标签则直接采取默认值compile，像下面这样。 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter</artifactId> <version>2.5.2</version> &l
深入探究Maven 3.5.0版本的核心功能与资源
2. 构建生命周期：Maven定义了三个主要的构建生命周期：清理、编译、测试、打包、安装、部署。 3. 插件和目标：Maven通过插件机制来执行实际的构建工作，一个插件可以包含多个目标，每个目标对应构建生命周期中的一...
maven_package 依赖包（完整）
07-24
maven 依赖包（完整）适合大多数项目，如：log4j-1.2.17.jar等
Maven项目打包成war包部署到Tomcat的方法
热门推荐
elice_的博客
12-03 1万+
转自：Maven项目打包成war包部署到Tomcat的方法_java_脚本之家 有关于 Maven 项目的打包部署，我这里用的是 Eclipse 编辑器，以此来做个简单的记录。 实践环境 操作系统： Windows IDE： Eclipse 打包部署过程　 1 项目打包 1.1 右键点击所需要打包的项目，点击如图所示 Maven clean，这里 Maven 会清楚掉之前对这个项目所...
Maven打包
cxy1991xm的博客
01-22 888
一、maven命令 1、clean：清空生成的文件 2、compile：编译 3、package：获取编译后的代码，并按照可发布的格式进行打包，例如 JAR、WAR或者EAR文件。 4、install：安装工程包到本地仓库中，该仓库可以作为本地其他工程的依赖。 将jar安装到本地仓库：mvn install:install-file -Dfile=jar包的位置 -DgroupId=ja...
maven的打包
说好的
11-02 523
1.首先为什么要打包 对于企业级项目，无论是进行本地测试还是测试环境测试，最终都要设计到项目的打包。 对于不同的环境下的项目打包，对应的项目所需要配置的资源不同，打包方式也有多种（比如ant，idea自带打包等），但是当项目很大，而且需要的外界配置很多时，打包操作也非常复杂，对于maven项目，我们可以通过pom.xml配置的方式来实现打包的环境选择，所以较其他的打包工具，maven只需要简单的配置就能完成不同环境的打包，还是很方便的。 2.打包操作步骤 ·建立对应的项...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值