On 8/24/07, Barrie Treloar <[EMAIL PROTECTED]> wrote: > On 8/24/07, Zarick Lau <[EMAIL PROTECTED]> wrote: > > Dear Users and Developers, > > > > In a multi-module project (1 parent with 2 sub-module), > > sub-module-b deps on sub-module-a, when I run maven under > > the top-level (parent), > > > > mvn process-resources > > > > Maven will try to grab sub-module-a from repository, as I > > haven't install / deploy sub-module-a, the build failed. > > > > However, if I invoke maven with: > > > > mvn package > > > > The whole build completed without error.. > > > > Any clues why this strange behavior happens? > > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > > However you need "install" to get your artifacts into the local > repository and package is _prior_ to install.
I know what 'install' mean in maven, but running mvn at the "parent" module doesn't require "installing" all sub-module first. And indeed, [Off topic] if running "install" in each individual module is pre-req, even though I run mvn at "parent" module, it looks a little bit strange for me... > > It doesn't make sense that process-resources should work when package does. Yes, I think so :) > > Maybe one of your plugins is failing because it is being run in a > phase before process-resources but requires some resolution available > in a later phase. > > Can you paste the error message? I can reproduce the issue, if sub-module-b packaing == jar, no error. My error occur only when packagin == ear... Thanks! Best regards, Zarick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
