anchor.diff:        }
   ----
   
  -Next we want to get hold of the project configuration to check whether automatic auditing was selected by the user. It
  -was easy in the `AbstractProjectCommand` descendants to get the selected project with the respective utility method and
  -then to obtain the configuration facet from there. Now we have to go through the `Projects.getSelectedProject` static
  -factory method for that. It needs to get a project factory, which luckily we can inject. It would be also safe to check
  -whether it is null and only then proceed to the entity instrumentation:
  +Next we want to get hold of the project configuration to check whether automatic auditing was selected by the user. It was easy in the `AbstractProjectCommand` descendants to get the selected project with the respective utility method and then to obtain the configuration facet from there. Now we have to go through the `Projects.getSelectedProject` static factory method for that. It needs to get a project factory, which luckily we can inject. It would be also safe to check whether it is null and only then proceed to the entity instrumentation:
   
   [source, java]
   ----
  
positive.code: [envers]$ addon-new-ui-command --named EnversSetupCommand --commandName "Envers: Setup" --categories "Auditing"
  ----
  
  While from the JBDS, after opening the Forge wizard (Ctrl + 4 or CMD + 4 on Mac), you should choose _Addon: New UI Command_
  and enter _EnversSetupCommand_ in the Type Name field, _Envers: Setup_ in the Command name field and add _Auditing_ to
  the Categories list box: +
  
  image::developing/forge-envers-setup-command.png[title="Creating _Envers: Setup_ command"]
  
  This will generate `EnversSetupCommand` class in the `org.jboss.forge.addon.commands` package (unless you didn't specify
  explicitly anything else). Forge makes this class extend `AbstractUICommand`, which provides some basic functionality
  like configuring the command name, the command dialog and the command execution. We will go through these in this and
  the next few sections. +
  
  The `getMetadata()` method should be already implemented by Forge:
  
  [source, java]
  ----
  
negative.code:    }
  ----
  
  In Forge you can also set default values for inputs. This way you can omit specifying its value on the command line and in the IDE it will be pre-filled in the command dialog. You can do that with the `setDefaultValue` method of the `UIInput`. In our case the UIInput is generified over the `org.jboss.forge.addon.parser.java.resources.JavaResource` class, so we'll have to check whether the current selection in the UI (being the CLI or JBDS) is a file that represents a Java type. If yes, we will set it as the default value of the text field:
  
  [source, java]
  ----
  