Also, if you have a META-INF/MANIFEST.MF with a `Class-Path` entry, you
don't have a uber jar :-)
You have an old school executable jar with hardcoded classpath.
Joakim Erdfelt / joa...@webtide.com
On Wed, Mar 7, 2018 at 11:14 AM, Joakim Erdfelt wrote:
> Don't forget to
Don't forget to merge the META-INF/services/ files too.
Joakim Erdfelt / joa...@webtide.com
On Wed, Mar 7, 2018 at 11:11 AM, west suhanic
wrote:
> Hello All:
>
> I am able to build an uber jar called x.jar via a makefile. The steps are:
>
> 1)Build a manifest file with
Hello All:
I am able to build an uber jar called x.jar via a makefile. The steps are:
1)Build a manifest file with the necessary classpaths specified. Here is
one I auto generate. I have simply
shortened it for this example. The key bit is to have one space after the
colon which terminates
Using makefile you'll have a lot of extra work to do with merging various
files for this executable jar (aka uber-jar).
There are 2 example projects we maintain, but they use maven and the
various plugins that do the merging for us in a smart fashion.
If you are working with