anchor.diff:                  has finished the task.
   ----
   
  -== Command `pm`
  -
  -Provisions an installation at the specified location by reading its
  -specification from the specified provisioning XML file.
  -
  -Arguments:
  -  
  -[source,shell]
  -----
  ---provisioning-xml - filesystem path to the provisioning XML file which
  -                     defines an installation in terms of the feature-packs
  -
  ---install-dir      - root directory for the installation to be provisioned
  -----
  -
  -Assuming the feature-packs are built and installed into the Maven repository,
  -these are the commands I use to test provisioning WildFly builds:
  -
  -[source,shell]
  -----
  -[pm] pm --install-dir install/wf-full --provisioning-xml tool/src/test/resources/wf-full-provisioning.xml
  -[pm] pm --install-dir install/wf-web --provisioning-xml tool/src/test/resources/wf-web-provisioning.xml
  -[pm] pm --install-dir install/wf-core --provisioning-xml tool/src/test/resources/wf-core-provisioning.xml
  -----
  -
   = Building and launching the tool
    
   The tool can be built by executing the following Maven command:
  
positive.code: 
  == Module `feature-pack-build-maven-plugin`
  
  Maven Mojo implementations (i.e. goals in Maven plugins).
  
  == Module `wildfly-feature-pack-maven-plugin`
  
  
negative.code:   
  * Build feature-packs and install them into the Maven repository;
  * Provision an installation by pulling the feature-packs from the
    Maven repository and installing them at the specified location.;
  * View the currently provisioned installation specification;
  * Export the currently provisioned installation specification to
    a file with goal to reproduce the installation later.
  
  The Maven assembly plug-in is configured to create a single executable JAR
  file which contains all the dependencies.
  
  = CLI Commands
  
  == FileSystem commands
  
  The following filesystem commands are available:
  
  * cd - change current work directory
  * pwd - print current work directory
  * mkdir - create a new directory if it does not already exist
  * ls - list the content of a directory
  * less - display the content of a file
  * rm - remove a file
  
  == provision-spec
  
  [source,shell]
  ----
  [workdir]$ provision-spec <spec-file-path> [--dir=<installation-dir>]
  ----
  
  (Re-)Provisions the installation according to installation specification
  provided in an XML file.
  
  Arguments:
  
  [source,shell]
  ----
  <path>        - filesystem path to the XML file describing the desired
                  installation specification.
  
  --dir         - optional, target installation directory. If the argument is
                  missing, the current work directory is assumed as the target.
  ----
  
  == install
  
  [source,shell]
  ----
  [workdir]$ install <feature-pack-gav> [--dir=<installation-dir>]
  ----
  
  Adds the feature-pack to the installation specification (or creates a new spec
  if one does not exist yet) and (re-)provisions the target installation.
  
  Arguments:
  
  [source,shell]
  ----
  <feature-pack-gav>  - groupId:artifactId:version of the feature-pack to install.
  
  --dir         - optional, target installation directory. If the argument is
                  missing, the current work directory is assumed as the target.
  ----
  
  == uninstall
  
  [source,shell]
  ----
  [workdir]$ uninstall <feature-pack-gav> [--dir=<installation-dir>]
  ----
  
  Removes the feature-pack from the installation specification and
  (re-)provisions the target installation.
  
  Arguments:
  
  [source,shell]
  ----
  <feature-pack-gav>  - groupId:artifactId:version of the feature-pack to
                        uninstall.
  
  --dir         - optional, target installation directory. If the argument is
                  missing, the current work directory is assumed as the target.
  ----
  
  == provisioned-spec
  
  === provisioned-spec display
  
  [source,shell]
  ----
  [workdir]$ provisioned-spec display [--verbose] [--dir=<installation-dir>]
  ----
  
  Displays the currently provisioned installation specification.
  
  Arguments:
  
  [source,shell]
  ----
  --verbose(-v) - whether to include feature-packs not explicitly chosen by
                  the user but installed as dependencies of other feature-packs.
  
  --dir         - optional, target installation directory. If the argument is
                  missing, the current work directory is assumed as the target.
  ----
  
  === provisioned-spec export
  
  [source,shell]
  ----
  [workdir]$ provisioned-spec export <file-path>
  ----
  
  Exports the currently provisioned installation specification to the specified
  file in the XML format. The resulting file can be used as an argument to
  `provision-spec` command.
  
  Arguments:
  
  [source,shell]
  ----
  <file-path>   - file path to store the provisioned specification to.
  ----
  
  == Command `feature-pack --action install`
  
  NOTE: this command is a work in progress! Don't try to use it w/o supervision!
  
  Builds a feature pack for the specified WildFly-based installation and
  installs the feature pack into the Maven repository.
  