How do I put all required JAR files in a library folder inside the final JAR file with Maven? How do I put all required JAR files in a library folder inside the final JAR file with Maven? java java

How do I put all required JAR files in a library folder inside the final JAR file with Maven?


The following is my solution. Test it if it works for you:

<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}/classes/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>test.org.Cliente</mainClass> -->            </manifest>            <manifestEntries>                <Class-Path>lib/</Class-Path>            </manifestEntries>        </archive>    </configuration></plugin>

The first plugin puts all dependencies in the target/classes/lib folder, and the second one includes the library folder in the final JAR file, and configures the Manifest.mf file.

But then you will need to add custom classloading code to load the JAR files.

Or, to avoid custom classloading, you can use "${project.build.directory}/lib, but in this case, you don't have dependencies inside the final JAR file, which defeats the purpose.

It's been two years since the question was asked. The problem of nested JAR files persists nevertheless. I hope it helps somebody.


Updated:

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


The simplest and the most efficient way is to use an uber plugin like this:

          <plugin>            <groupId>org.apache.maven.plugins</groupId>            <artifactId>maven-shade-plugin</artifactId>            <executions>                <execution>                    <phase>package</phase>                    <goals>                        <goal>shade</goal>                    </goals>                </execution>            </executions>            <configuration>                <finalName>uber-${project.artifactId}-${project.version}</finalName>            </configuration>        </plugin>

You will have de-normalized all in one JAR file.