anchor.diff:  [[repackage-layers]]
   === Layered jars
   A repackaged jar contains the application's classes and dependencies in `BOOT-INF/classes` and `BOOT-INF/lib` respectively.
  -For cases where a docker image needs to be built from the contents of the jar, it's useful to be able to separate these folders futher so that they can be written into distinct layers.
  +For cases where a docker image needs to be built from the contents of the jar, it's useful to be able to separate these folders further so that they can be written into distinct layers.
   
   Layered jars use the same layout as regular repackaged jars, but include an additional meta-data file that describes each layer.
   To use this feature, the layering feature must be enabled:
  
positive.code: ----
  
  The configuration file describes how the jar can be separated into layers, and the order of those layers.
  The following example shows how the default ordering described above can be defined explicity:
  
  [source,xml,indent=0,subs="verbatim,attributes"]
  ----
  
negative.code: 
  [[repackage-layered-jars-additional-layers]]
  ==== Custom layers configuration
  The default setup splits dependencies into snapshot and non-snapshot, however, you may have more complex rules.
  For example, you may want to isolate company-specific dependencies of your project in a dedicated layer.
  The following `layers.xml` configuration shown one such setup:
  
  