From f2dfb040abb7e43b9e3beddaf23f2f15c771d6b8 Mon Sep 17 00:00:00 2001 From: Matt Benson Date: Wed, 24 Jun 2015 11:22:30 -0500 Subject: [PATCH] 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 --- spring-boot-docs/src/main/asciidoc/getting-started.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-boot-docs/src/main/asciidoc/getting-started.adoc b/spring-boot-docs/src/main/asciidoc/getting-started.adoc index c615f5f3dd4..d66ef866752 100644 --- a/spring-boot-docs/src/main/asciidoc/getting-started.adoc +++ b/spring-boot-docs/src/main/asciidoc/getting-started.adoc @@ -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.