anchor.diff:  . Use Maven to resolve and copy the dependencies to the `target` folder, and copy `joda-time-2.4.jar` to the module directory.
   
    $ mvn dependency:copy-dependencies
  - $ cp target/dependency/joda-time-2.4.jar $EAP_HOME/modules/org/joda/time/2.4/
  -
  -. Update the `jboss-deployment-structure.xml` to use the correct module and slot.
  + $ cp target/dependency/joda-time-2.4.jar $JBOSS_HOME/modules/org/joda/time/2.4/
  +
  +. Update the `jboss-deployment-structure.xml` to use the correct module name and slot.
   +
   [source,xml]
   ----
  
positive.code: }
  ----
  
  . Test the application. The servlet should display the current month: http://localhost:8080/jboss-helloworld/HelloWorld
  
  . Verify the jar exists in the war.
  
  
negative.code: 22:12:00,743 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC000001: Failed to start service jboss.deployment.unit."jboss-helloworld.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-helloworld.war".POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "jboss-helloworld.war"
  ...
  Caused by: java.lang.ClassNotFoundException: org.joda.time.LocalDate from [Module "deployment.jboss-helloworld.war:main" from Service Module Loader]
  ----
  +
  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
  ----
  
  . Add a `jboss-deployment-structure.xml` that specifies a dependency on the joda-time module.
  