diff --git a/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/repackage-classifier.apt.vm b/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/repackage-classifier.apt.vm index 5f3ebcfb668..b47137d1eed 100644 --- a/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/repackage-classifier.apt.vm +++ b/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/repackage-classifier.apt.vm @@ -7,8 +7,14 @@ ----- By default, the <<>> goal will replace the original artifact with the - executable one. If you prefer to keep the original artifact and attach the executable - one with a different classifier, configure the plugin as follows: + repackaged one. That's a sane behaviour for modules that represent an app but if + your module is used as a dependency of another module, you need to provide a + classifier for the repackaged one. + + The reason for that is that application classes are packaged in <<>> + so that the dependent module cannot load a repackaged jar's classes. If that is the + case or if you prefer to keep the original artifact and attach the repackaged one + with a different classifier, configure the plugin as follows: --- @@ -41,8 +47,8 @@ --- - This configuration will generate two artifacts: the original one and the executable counter - part produced by the repackage goal. Both will be installed/deployed accordingly. + This configuration will generate two artifacts: the original one and the repackaged counter + part produced by the repackage goal. Both will be installed/deployed transparently.