title: What is the difference between "mvn deploy" to a local repo and "mvn install"?
body: <p>My team uses an internal team maven repo that is shared from a development server using Apache. We also run the Continuum CI server on the same machine. Maven builds in Continuum are run with the &quot;install&quot; goal, which copies the final artifact directly into the shared directory.</p>
  <p>The question is, what is the difference between adding files to the shared repo using <code>mvn install</code> and using the deploy goal (mvn-deploy plugin)?</p>
  <p>It seems to me that using <code>mvn deploy</code> creates additional configuration hassles, but I have read somewhere that installing files into a shared repo is a bad idea for some reason related to the internal workings of maven.</p>
  <p>update: I get the functional differences between <code>deploy</code> and <code>install</code>; I am actually more interested in the low level details in terms of what files are created in the maven repo.</p>