anchor.diff:  
   
   [[build-tool-plugins-maven-packaging]]
  -=== Packaging executable jar and war files
  -Once `spring-boot-maven-plugin` has been included in your `pom.xml` it will automatically
  -attempt to rewrite archives to make them executable using the `spring-boot:repackage`
  -goal. You should configure your project to build a jar or war (as appropriate) using the
  -usual `packaging` element:
  +=== Packaging Executable Jar and War Files
  +Once `spring-boot-maven-plugin` has been included in your `pom.xml`, it automatically
  +tries to rewrite archives to make them executable by using the `spring-boot:repackage`
  +goal. You should configure your project to build a jar or war (as appropriate) by using
  +the usual `packaging` element, as shown in the following example:
   
   [source,xml,indent=0,subs="verbatim,attributes"]
   ----
  
positive.code: ----
  
  
  
  === spring-boot:findmainclass
  The `findmainclass` task is used internally by `exejar` to locate a class declaring a
  `main`. You can also use this task directly in your build if needed. The following
  attributes are supported
  
  [cols="1,2,2"]
  |====
  
negative.code: 	$ java -jar target/mymodule-0.0.1-SNAPSHOT.jar
  ----
  
  To build a war file that is both executable and deployable into an external container, you
  need to mark the embedded container dependencies as "`provided`", as shown in the
  following example:
  
  [source,xml,indent=0,subs="verbatim,attributes"]
  ----
  