The assembly:assembly mojo is meant to be run directly from the command
line. It takes care of running the build lifecycle up to the point it needs,
then invoking its own behavior. Therefore, if it's bound to the lifecycle,
it can result in weirdness. If you want this behavior (meaning the
assembly-as-part-of-the-lifecycle thing), you might want to use the
assembly:attached mojo instead, like this:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
[...]
<executions>
<execution>
<id>attach assembly</id>
<phase>packaging</phase>
<goals><goal>attached</goal></goals>
</execution>
</executions>
</plugin>
HTH,
-john
On 8/8/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote:
I tried to bind assembly to the package phase and I get this error.
[INFO] Mojo: 'assembly' requires direct invocation. It cannot be used as
part of the lifecycle (it was included via the POM).
First off... why not?
Secondly, is there another alternative?
-----Original Message-----
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 08, 2006 3:05 PM
To: Maven Users List
Subject: Re: Assembly madness...
Okay, so what I'm reading from this conversation is that you want to:
a. have a multimodule build
b. wrap the <modules/> up in an assembly
First question: why not do the build and assembly all in one step? Why
install the modules to a repository first? When the assembly descriptor
references a <moduleSet/> it's talking about a set of <module/> entries in
the current POM. If it's including binaries of those modules, they will
have
to be built.
If you're not doing a true multimodule build here, why not use a
dependencySet instead? Dependencies are resolved from the repository, not
modules.
Finally: When you perform this multimodule build targeting different JVMs,
how do you specify the classifiers to use in tagging the output jars? Is
this - and the compiler configuration that I assume you're changing too -
injected into the build(s) via profile, or...?
-john
On 8/8/06, mike7 <[EMAIL PROTECTED]> wrote:
>
>
> Aggregator project = parent pom that refers to modules to be built.
> Are you using maven 2????
> --
> View this message in context:
> http://www.nabble.com/Assembly-madness...-tf2070731.html#a5713721
> Sent from the Maven - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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]
