That worked, thanks Tim!
Tim O'Brien wrote:
Frank,
In Project C's pom.xml, use the "single" goal instead of the
"assembly" goal. This should fix the problem.
Tim
On Tue, Apr 13, 2010 at 12:01 PM, Frank Maritato
<[email protected]> wrote:
Hi All,
I have a multi module project and my "mvn package" command from the top
level is failing when one of my modules defines the assembly plugin with an
<executions> block to make it part of the package phase. Specifically you
will see that moduleC cannot resolve the artifact in moduleA and it looks
like the unit tests are being run twice. When I comment out the executions
block it all works as expected (except that I need a separate step to do my
assembly).
I put together a simple project that illustrates the problem and attached it
to this message. Is this a known issue? Intended behavior? Am I just doing
it wrong? Any help would be appreciated.
Thanks!
--
Frank Maritato
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
