thanks dan. my assembly config is in a parent pom, and when i try to configure
the binding (i was using assembly:assembly, don't know if that make a
difference) i could not install or deploy the pom due to the below error. is
there a way to stop stop this or do i need to configure the assembly in the
project poms (rather than in the parent).
[INFO] [assembly:assembly {execution: default}]
[INFO]
------------------------------------------------------------------------
----
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
----
[INFO] Error creating assembly
Embedded error: c:\dev\workspace\ServerAppPom\target isn't a directory
jake
-----Original Message-----
From: dan tran [mailto:[EMAIL PROTECTED]
Sent: Fri 5/5/2006 6:31 PM
To: Maven Users List
Subject: Re: M2: Assembly Plugin Breaks Module Build
for project that requires assembly, bind assembly:attached to the package
phase, then you run
maven deploy
-D
On 5/5/06, Jake Pezaro <[EMAIL PROTECTED]> wrote:
>
> We have a number of projects which we build nightly using maven. I have
> grouped these together using modules so that i can build & deploy them
> all at once with one command (mvn assembly:assembly deploy).
>
> The problem is that the build fails because the assembly:assembly target
> requires all projects to have an assembly defined. Is there a way
> around this?
>
> thanks
>
> jake
>
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
