title: Why Maven asks me for distribution config in every module in multi-module site deployment?
body: <p>My multi-module Maven project looks like:</p>
  
  <pre><code>/foo
    pom.xml
    /foo-parent
    /foo-core
    /foo-something
    /src
      /site
  </code></pre>
  
  <p>Pay attention that <code>foo</code> is not a parent project, but <code>foo-parent</code> is (for <code>foo-core</code> and <code>foo-something</code>). <code>foo</code> is not inheriting from <code>foo-parent</code>. Site configuration is stored in <code>foo</code>. All other sub-modules don't know anything about project site and don't have <code>&lt;distributionManagement&gt;</code>. mvn site works perfect,  and now I'm running <code>mvn site-deploy</code>:</p>
  
  <pre><code>[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:2.0.1:deploy
  (default-deploy) on project foo-parent: Missing site information in the 
  distribution management element in the project.. -&gt; [Help 1]
  </code></pre>
  
  <p>Maven is trying to <code>site-deploy</code> every sub-module individually?? Is it a correct behavior?</p>