anchor.diff:     }
   ----
   
  -Finally, we want to avoid some compilation errors in the project where we will run this command. So it should be only
  -available for execution if the user has called the setup command first, i.e. if the current project has dependency to
  -Hibernate Envers. You can implement this enabling and disabling in several ways. We will show one of these: by
  -implementing the `isEnabled` method. There we will again obtain the `DependencyFacet` and will ask it whether the
  -desired dependency is installed. If this method returns false, the Forge commands wizard will not list the Audit entity
  -command and it will not be available in the command completion in CLI. This is the implementation:
  +Finally, we want to avoid some compilation errors in the project where we will run this command. So it should be only available for execution if the user has called the setup command first, i.e. if the current project has dependency to Hibernate Envers. You can implement this enabling and disabling in several ways. We will show one of these: by implementing the `isEnabled` method. There we will again obtain the `DependencyFacet` and will ask it whether the desired dependency is installed. If this method returns false, the Forge commands wizard will not list the Audit entity command and it will not be available in the command completion in CLI. This is the implementation:
   
   [source, java]
   ----
  
positive.code: {
  ----
  
  We will have to implement two more abstract methods coming from this parent class:
  
  [source, java]
  ----
  
negative.code:    }
  ----
  
  Next we will check whether the chosen class has already the `Audited` annotation and if not, will add it to that. At the end we'll save the new content and will return successful result:
  
  [source, java]
  ----
  