title: Vagrant & Maven Plugin strange behaviour
body: <p>I've set up a Vagrant VM running Java/Maven/Tomcat. I've then taken an application I'm working on and copied the war to the shared folder that the VM has access to, namely webapps. I hunted around as didn't want to be copy / pasting when it should be automated and found reference to a maven plugin:</p>
  
  <pre><code>  &lt;plugins&gt;
        &lt;plugin&gt;
            &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
            &lt;artifactId&gt;maven-war-plugin&lt;/artifactId&gt;
            &lt;configuration&gt;
                &lt;outputDirectory&gt;/Username/Development/temp/vagrant-tomcat-2/vagrant-ubuntu-tomcat7/tomcat/webapps&lt;/outputDirectory&gt;
            &lt;/configuration&gt;
        &lt;/plugin&gt;
    &lt;/plugins&gt;
  </code></pre>
  
  <p>I've added this to my build. Made a simple change to the index and ran clean install. My console panel looks as I'd expect it to, the war is being copied across - magic.</p>
  
  <pre><code>[INFO] Installing Username/Development/temp/vagrant-tomcat-2/vagrant-
  
  ubuntu-tomcat7/tomcat/webapps/FitnessTracker.war to Username/.m2/repository/com/pluralsight/FitnessTracker/0.0.1-SNAPSHOT/FitnessTracker-0.0.1-SNAPSHOT.war
  [INFO] Installing Username/Development/temp/vagrant-tomcat-2/Spring Tutorial - JPA Hibernate/spring_mvc_base-master/pom.xml to Username/.m2/repository/com/pluralsight/FitnessTracker/0.0.1-SNAPSHOT/FitnessTracker-0.0.1-SNAPSHOT.pom
  </code></pre>
  
  <p>I then reload the port and get a resource is not available error.  Commenting out the plugin and running clean install again has the effect of copying the last changes I made to the webapp folder so that If I then check the port I'll see the changes.</p>
  
  <p>What am I missing? I'm certain it's something daft.  </p>
  
  <p>The short short version: the maven plugin appears to be copying the last updated war instead of the current one, I think.</p>