@@ -373,9 +373,9 @@ Running this way makes your static classpath resources (i.e. in `src/main/resour
373
373
default) reloadable in the live application, which can be helpful at development time.
374
374
375
375
[[build-tool-plugins-gradle-global-configuration]]
376
- === Spring Boot Plugin configuration
376
+ === Spring Boot plugin configuration
377
377
The gradle plugin automatically extends your build script DSL with a `springBoot` element
378
- for global configuration of the Boot plugin. Set the appropriate properties as you would
378
+ for global configuration of the Boot plugin. Set the appropriate properties as you would
379
379
with any other Gradle extension (see below for a list of configuration options):
380
380
381
381
[source,groovy,indent=0,subs="verbatim,attributes"]
@@ -386,6 +386,7 @@ with any other Gradle extension (see below for a list of configuration options):
386
386
----
387
387
388
388
389
+
389
390
[[build-tool-plugins-gradle-repackage-configuration]]
390
391
=== Repackage configuration
391
392
The plugin adds a `bootRepackage` task which you can also configure directly, e.g.:
@@ -407,27 +408,28 @@ The following configuration options are available:
407
408
|The main class that should be run. If not specified the `mainClassName` project property
408
409
will be used or, if the no `mainClassName` id defined the archive will be searched for a
409
410
suitable class. "Suitable" means a unique class with a well-formed `main()` method (if
410
- more than one is found the build will fail). You should also be able to specify the main
411
- class name via the "run" task (`main` property) and/or the "startScripts" (`mainClassName`
412
- property) as an alternative to using the "springBoot" configuration.
411
+ more than one is found the build will fail). You should also be able to specify the main
412
+ class name via the "run" task (`main` property) and/or the "startScripts"
413
+ (`mainClassName` property) as an alternative to using the "springBoot" configuration.
413
414
414
415
|`classifier`
415
416
|A file name segment (before the extension) to add to the archive, so that the original is
416
- preserved in its original location. Defaults to null in which case the archive is repackaged
417
- in place. The default is convenient for many purposes, but if you want to use the
418
- original jar as a dependency in another project, it's best to use an extension to define the
419
- executable archive.
417
+ preserved in its original location. Defaults to null in which case the archive is
418
+ repackaged in place. The default is convenient for many purposes, but if you want to use
419
+ the original jar as a dependency in another project, it's best to use an extension to
420
+ define the executable archive.
420
421
421
422
|`withJarTask`
422
- |The name of the `Jar` task (defaults to all) which is used to locate the archive to repackage.
423
+ |The name of the `Jar` task (defaults to all) which is used to locate the archive to
424
+ repackage.
423
425
424
426
|`customConfiguration`
425
427
|The name of the custom configuration whuch is used to populate the nested lib directory
426
- (without specifying this you get all compile and runtime dependencies).
427
-
428
+ (without specifying this you get all compile and runtime dependencies).
428
429
|===
429
430
430
431
432
+
431
433
[[build-tool-plugins-gradle-repackage-custom-configuration]]
432
434
=== Repackage with custom Gradle configuration
433
435
Sometimes it may be more appropriate to not package default dependencies resolved from
0 commit comments