title: Isn't maven-deploy-plugin aware of the pom in which I declared it as a build plugin?
body: <p>I have a maven project. In the pom I declared the group id, artifact id, version.</p>
  
  <p>I declared for maven-deploy-plugin as a build plugin, with goal of deploy:deploy-file.</p>
  
  <p>Then I launched maven from eclipse with the same goal, wuth -Durl declared as jvm arg.</p>
  
  <p>Maven build fails saying I did not supply groupid, artifactid, package, file not defined.</p>
  
  <p>Why doesn't it get those values from the pom?</p>
  
  <p>There must be a way ti tell the plugin to use the pom values, right? Because the maven people certainly believe in DIE-DRY - duplication is evil, don't repeat yourself? Otherwise, I could create an artefact distribution that contradicts its pom?</p>
  
  <ol>
  <li><p>Why, doesn't the plugin know I wish to deploy the project, including the source and not just a single jar or pom?</p></li>
  <li><p>Why, doesn't the plugin know it should just look at the pom artifactid declaration to get the groupid and artifactid.</p></li>
  </ol>
  
  <p>Rant:</p>
  
  <ul>
  <li>If these features are missing, though I strongly hope they are not mmissing - Why, doesn't the plugin developer feel these are important features?</li>
  </ul>