Update documentation to remove 'shaded jar' term

Update documentation section that discusses uber jars since it conflates
the concepts of the uber jar and the shading of dependencies into jars
(which may or may not be true uber jars).

Fixes gh-3321
This commit is contained in:
Matt Benson 2015-06-24 11:22:30 -05:00 committed by Phillip Webb
parent 98ce54c4c3
commit f2dfb040ab
1 changed files with 2 additions and 2 deletions

View File

@ -702,8 +702,8 @@ Java does not provide any standard way to load nested jar files (i.e. jar files
themselves contained within a jar). This can be problematic if you are looking to
distribute a self-contained application.
To solve this problem, many developers use "`shaded`" jars. A shaded jar simply packages
all classes, from all jars, into a single "`uber jar`". The problem with shaded jars is that
To solve this problem, many developers use "`uber`" jars. An uber jar simply packages
all classes, from all jars, into a single archive. The problem with this approach is that
it becomes hard to see which libraries you are actually using in your application. It can
also be problematic if the the same filename is used (but with different content) in
multiple jars.