anchor.diff:  that method. If config is read at runtime, Substrate cannot reason about the contents of the config and so needs to keep all features in case they are required.
   
   
  -== Maven setup
  +=== Maven setup
   
   Your extension project should be setup as a multi-module project with two submodules:
   
  
positive.code: `io.quarkus.deployment.builditem.substrate.SubstrateConfigBuildItem`::
  A convenience feature that allows you to control most of the above features from a single build item.
  
  == IDE support tips
  
  === Writing {project-name} extensions in Eclipse
  
  The only particular aspect of writing {project-name} extensions in Eclipse is that APT (Annotation Processing Tool) is required as part of extension builds, which means you need to:
  
  
negative.code: 
  TODO: config integration
  
  === CDI Extension Points
  As a CDI based runtime, {project-name} extensions often make CDI beans available as part of the extension behavior. The link:cdi-reference.html[Build Time Extension Points] describes the `BuildItems` you can make use of in your extension build steps to achieve this.
  
  === Testing Extensions
  
  Testing of extensions should be done with the `io.quarkus.test.QuarkusUnitTest` runner. This runner allows
  for Arquillian-style tests that test specific functionalities. It is not intended for testing user applications, as this
  