anchor.diff:      com.mycorp.libx.autoconfigure.LibXWebAutoConfiguration
   ----
   
  -TIP: You can use comments via `#` in this file.
  -
  -NOTE: Auto-configurations must be loaded that way _only_.
  +TIP: You can add comments to the imports file using the `#` character.
  +
  +NOTE: Auto-configurations must be loaded _only_ by being named in the imports file.
   Make sure that they are defined in a specific package space and that they are never the target of component scanning.
   Furthermore, auto-configuration classes should not enable component scanning to find additional components.
   Specific ``@Import``s should be used instead.
   
  -You can use the {spring-boot-autoconfigure-module-code}/AutoConfigureAfter.java[`@AutoConfigureAfter`] or {spring-boot-autoconfigure-module-code}/AutoConfigureBefore.java[`@AutoConfigureBefore`] annotations if your configuration needs to be applied in a specific order.
  +If your configuration needs to be applied in a specific order, you can use the `before`, `beforeName`, `after` and `afterName` attributes on the {spring-boot-autoconfigure-module-code}/AutoConfiguration.java[`@AutoConfiguration`] annotation or the dedicated {spring-boot-autoconfigure-module-code}/AutoConfigureBefore.java[`@AutoConfigureBefore`] and {spring-boot-autoconfigure-module-code}/AutoConfigureAfter.java[`@AutoConfigureAfter`] annotations.
   For example, if you provide web-specific configuration, your class may need to be applied after `WebMvcAutoConfiguration`.
  -
  -TIP: If you are using the {spring-boot-autoconfigure-module-code}/AutoConfiguration.java[`@AutoConfiguration`] annotation, you can use the `before`, `beforeName`, `after` and `afterName` attribute aliases instead of the dedicated annotations.
   
   If you want to order certain auto-configurations that should not have any direct knowledge of each other, you can also use `@AutoConfigureOrder`.
   That annotation has the same semantic as the regular `@Order` annotation but provides a dedicated order for auto-configuration classes.
  
positive.code: === Locating Auto-configuration Candidates
  
  Spring Boot checks for the presence of a `META-INF/spring/org.springframework.boot.autoconfigure.AutoConfiguration.imports` file within your published jar.
  The file should list your configuration classes, as shown in the following example:
  
  [indent=0]
  ----
  
negative.code: 	</project>
  ----
  
  With Gradle, the dependency should be declared in the `annotationProcessor` configuration, as shown in the following example:
  
  [source,gradle,indent=0,subs="verbatim"]
  ----
  