anchor.diff:  This is expected becuase provided scope tells Maven not to include the dependency in the WAR, because it will be provided at runtime by some other means. We can verify the JAR is not included by checking the WEB-INF/lib directory. It is not found since this WAR no longer includes any dependencies.
   +
   ----
  -ls target/jboss-helloworld/WEB-INF/lib
  -ls: cannot access target/jboss-helloworld/WEB-INF/lib/: No such file or directory
  +$ ls target/jboss-helloworld/WEB-INF/lib
  +$ ls: cannot access target/jboss-helloworld/WEB-INF/lib/: No such file or directory
   ----
   
   . Add a `jboss-deployment-structure.xml` that specifies a dependency on the joda-time module.
  
positive.code: +
  To deploy the JAR using the CLI, use the following:
  +
   cd common-utils
   mvn clean install
   $JBOSS_HOME/bin/jboss-cli.sh -c "deploy target/common-utils-1.0.jar"
  
  . Verify that the deployment was successful:
  +
  
negative.code: 
  . Create an EAR project for the dynamic module named common-module.
  +
   $ cd dynamic-ear
   $ mkdir common-module
  
  . Create a pom for the common-module project. Include common-utils as a dependency.
  +
  