root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions 12 Packages Projects Releases Wiki Activity

Polish 

See gh-6792
This commit is contained in:
Stephane Nicoll 2016-08-31 09:27:50 +02:00
parent b0face34f4
commit cf07d19ed4
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
spring-boot-tools/spring-boot-maven-plugin/src/site/apt/examples/repackage-classifier.apt.vm
View File

@ -7,8 +7,14 @@
-----
By default, the <<<repackage>>> 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 <<<BOOT-INF/classes>>>
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:
---
<project>
@ -41,8 +47,8 @@
</project>
---
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.