I can tell you that. The reactor specifically exists for this purpose. However, the reactor is sensitive to what's been produced over the course of the build. There is no test-jar until the jar plugin runs to make the test jar, and your toplevel pom puts that in 'package'. If you moved that to compile, then all will be well.
It's a bit of a magic trick that the normal jar file is available without 'package', but maven has a certain number of magic tricks. On Tue, Oct 19, 2010 at 8:05 PM, Robert Matthews <[email protected]> wrote: > That make sense and it then builds. The question then remains though as to > why the main source's dependencies can be resolved without the jar files > being created. > > I have posted a message to the Maven guys about this, so lets see what they > come back with. > > Rob > > On 20/10/10 00:55, Benson Margulies wrote: >> >> My patch isn't needed. Just run mvn package so that the test-jar >> artifacts get created. >> > >
