mvn compile at the parent wont work. It compile fine module A first. But it does not install A into local repo so that module B can pickup. So correct way is
maven install -D On 12/24/05, Tom Huybrechts <[EMAIL PROTECTED]> wrote: > > Suppose I have a multi-module setup, with one parent project containing > two > modules moduleA and moduleB, and moduleB has a dependency on module A. > > If I do 'mvn compile' in the parent project, the compile for moduleB will > nicely use the output directory of moduleA on its classpath (after > compiling > moduleA off course). > > Now, is this also supposed to work when I start the compile from moduleB > itself, given that I have already manually done a compile in moduleA ? It > doesn't work for me, and it seems like maven has enough information > available to use the artifacts in moduleAs directory, without having to > install them in the local repository. > > Thanks, > > Tom > >
