From 26643ef4285e8b61577893b275f56433122b5650 Mon Sep 17 00:00:00 2001
From: Stephane Nicoll <snicoll@pivotal.io>
Date: Thu, 15 Dec 2016 15:28:25 +0100
Subject: [PATCH] Clarify how to exclude devtools with war packaging.

Closes gh-7556
---
 .../spring-boot-maven-plugin/src/site/apt/usage.apt.vm       | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm b/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm
index 5e501a2ada..3b2d1cdacb 100644
--- a/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm
+++ b/spring-boot-tools/spring-boot-maven-plugin/src/site/apt/usage.apt.vm
@@ -60,6 +60,11 @@ Usage
   Please note that the <<<outputFileNameMapping>>> feature of the <<<maven-war-plugin>>>
   is currently not supported.
 
+  It is also possible to automatically exclude devtools using the <<<excludeDevtools>>>
+  property. In order to make that work with <<<war>>> packaging, the
+  `spring-boot-devtools` dependency must be set as <<<optional>>> or with the
+  <<<provided>>> scope.
+
   The original (i.e. non executable) artifact is renamed to <<<.original>>> by default but it is also
   possible to keep the original artifact using a custom classifier.