title: Maven multi-module project - copying all "package" JARS from submodules into parent/target/
body: <p>I have a maven project with quite a few submodules.  What I am looking for is a way to get all the .jar files produced by the sub-modules included in the aggregating POM's /target/ directory, so they can be conveniently used afterwards. </p>
  
  <ul>
  <li>They don't need to be merged.  Preferably not, but if they <em>must</em> be then that is ok.</li>
  <li>Don't care about dependancies</li>
  <li>This is primarily for convenience, at this point</li>
  </ul>
  
  <p>A basic version of what I am looking at doing:</p>
  
  <pre><code>Prj1/pom.xml  =&gt;  prj1/target/proj1.jar  (and classes/generated-sources/etc)
  Prj2/pom.xml  =&gt;  prj2/target/proj2.jar
  Main/pom.xml  =&gt;
                    main/target/proj1.jar
                    main/target/proj2.jar
                    ... classes/generated-sources not needed at all,
                    ... but they could be combined here.  I assume they will be
  </code></pre>
  
  <p>I've been reading, and using some suggestions from SO as well.  So far I haven't found a way to do this, but I'm sure it is there.  </p>
  
  <p><strong>edit:</strong></p>
  
  <p>I've given up on getting this to work in a simple way, for all included subprojets.  The best answer I have so far is using the dependancy plugin to manually specify (again), each and every sub-module to be included.  The idea was to be able to configure the POMs easily for the dozens of clients, simply including the modules necessary and then having it magically stick all the sub-modules's jars in one location.  Maven is pretty nice, when you don't do much with it, but the angle bracket tax is incredible when you try.</p>
  
  <p>I still find it odd that such standard-seeming tasks (judging from the questions asked on SO, and what any normal project would do) are so difficult.  Is maven3 better? </p>