anchor.diff:  
   Static modules are good for creating common libraries that can be shared among multiple deployments--especially when those common libraries do not change often. But what if we have common libraries we want to make available, but also update as often as our application? Creating a dynamic module may be the right choice, since we can update it just like any other deployed artifact.
   
  -. Open the dynamic/helloworld/pom.xml file, and add a dependency on the common-utils library. This project is located at dynamic/common-utils. Set the scope to `provided`.
  +. Open the initial/helloworld/pom.xml file, and add a dependency on the common-utils library. This project is located at initial/common-utils. Set the scope to `provided`.
   +
   [source,xml]
  -.dynamic/helloworld/pom.xml
  +.initial/helloworld/pom.xml
   ----
   <dependency>
       <groupId>org.jboss.sample</groupId>
  
positive.code: 
  . Build, deploy, and test the helloworld application. The deployment should be successful and "WORLD" should be capitalized.
  +
   $ cd helloworld
   $ mvn clean package jboss-as:deploy
  
  . Congratulations! You have created a dynamic module that is easy to maintain alongside your application.
  
negative.code: 
   service jboss.module.spec.service."deployment.common-utils-1.0.jar".main (missing)...
  ====
  
  === Safely updating and redeploying dynamic modules
  
  TIP: TODO: include steps to redeploy dynamic modules and restarting/reloading appropriately
  
  TIP: TODO: same for domain mode
  
  TIP: TODO: add note about finalName and version numbers
  
  
  