Users List
Subject: Re: shade plugin usage
First, try to stay away from the überjar path. It's normally not the way to
go today, but you should use the jar and it's dependencies instead. I've
seen many case where people use a überjar just to try to make their life
simpler but ending up with other
: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf
Of Anders Hammar
Sent: Wednesday, September 04, 2013 2:08 AM
To: Maven Users List
Subject: Re: shade plugin usage
First, try to stay away from the überjar path. It's normally not the way
to
go today, but you
From: ctrue...@wisc.edu
Date: Thu, 5 Sep 2013 10:37:34 -0500
Subject: Re: shade plugin usage
To: users@maven.apache.org
Hi Anders,
Help the Java community kill all überjars...
Personally, I am a fan of uberjars MG+1 as long as the encapsulated
dependencies
are shaded to avoid
First, try to stay away from the überjar path. It's normally not the way to
go today, but you should use the jar and it's dependencies instead. I've
seen many case where people use a überjar just to try to make their life
simpler but ending up with other issues instead. A proper classpath is the
Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf
Of Anders Hammar
Sent: Wednesday, September 04, 2013 2:08 AM
To: Maven Users List
Subject: Re: shade plugin usage
First, try to stay away from the überjar path. It's normally not the way to
go today, but you should
I've a project that uses shade to create an uberjar - since I want that
uberjar artifact to be available for use in other projects, does it make
sense to *not* attach the artifact in shade, but rather have shade create
the uberjar and dependency-reduced-pom, and then use install:install-file to
