java - Create runnable jar with without repackaging dependencies - Stack Overflow

admin管理员组

文章数量:1344937

How to create a runnable jar (UberJar, FatJar) with Maven that

1. contains alls dependencies as origin jar files
2. can be executed by just calling 'java -jar myapp.jar' ?

TL;DR: I am currently working on an application that uses BouncyCastle and registers their SecurityProvider. When I use the maven-shade-plugin to create the UberJar, all jar files of all dependencies are exploded and their classes are repackaged. Unfortunately exactly this leads to a problem. While the application can be successfully executed with a JRE like Azul Zulu, execution fails with Oracle's JRE. Oracle only accepts SecurityProviders, which are contained in jar files with specific Signatures. Only jar files which are "signed with certificates" inside their own or Sun's PKI are accepted. (See: How to sign a custom JCE security provider answer by erickson).

What I could do, just out of the box:

• Define the precondition to use only specific JREs   ->   Bad "UserExperience"
• Create the UberJar differently, e.g. by storing all or some dependencies in a lib directory beside the executable jar and add this directory name as a classpathPrefix to the jar plugin   ->   Additional complexity on final result

Preferred solution: I want to create one ingle jar file which will be provided to the user, so he is not in the need to take care of additional directory structures and contents. In this single jar file I want to keep all (or if possible: only some defined) dependencies as origin jar files. The contents of those jar files shall be added to the classpath, equally to what happens when I create the final jar with the maven-shade-plugin which unfortunately explodes the jar files. For a JRE like Oracle is then must be possible to verify the signatures on the jar files which contain the SecurityProvider. -> Everybody (including Oracle) is happy.

So here the final question: How to configure a Maven build setup to create a runnable jar, that keeps some or all dependencies as origin and unmodified jar files, so that their contents (classes, signatures, etc.) can be accessed during runtime.

本文标签： javaCreate runnable jar with without repackaging dependenciesStack Overflow