I think that this is due to the @requiresDirectInvocation attribute in
the Assembly Mojo...
This seems to prevent you from defining multiple configurations using
multiple <execution> sections, since these appear to not be used when
directly invoking the mojo (only the <configuration> child of the
<plugin> element is used). You should be able to define a profile
with an alternate configuration for the assembly plugin:
<profiles>
<profile>
<id>Assembly-2</id>
<build>
<plugins>
<plugin>
...the other assembly plugin configuration...
</plugin>
</plugins>
</build>
</profile>
</profiles>
-Dan
On 10/11/05, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Ok, I thought that was the intent. I tried that before but I get an
> error saying that the assembly plugin can't be bound to a phase.
>
> -----Original Message-----
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 10, 2005 11:47 PM
> To: Maven Users List
> Subject: Re: [m2] multiple assemblies
>
> You need to use <executions> and bind to a phase of the lifecycle
> (probably package).
>
> You can have multiple executions in the lifecycle, but only one from the
> command line (or it wouldn't know which config to assign to which).
>
> - Brett
>
> On 10/11/05, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > Hello,
> > I followed the instructions to define an assembly inside my pom like
> > this:
> > <plugin>
> > <artifactId>maven-assembly-plugin</artifactId>
> > <version>2.0-beta-1</version>
> > <configuration>
> >
> > <descriptor>src/main/assembly/assembly.xml</descriptor>
> >
> > <finalName>${pom.artifactId}-${pom.version}</finalName>
> > <outputDirectory>target</outputDirectory>
> > <workDirectory>target/assembly/work</workDirectory>
> > </configuration>
> > </plugin>
> >
> > I'd like to define another assembly (coincidentally for uploading to
> > ibiblio) but even if I define my new xml on the command line, it
> > completely ignores me and builds my previously defined assembly. What
> > is the correct way to deal with multiple assemblies for the same
> project?
> >
> > Thanks.
> >
> >
>
> ---------------------------------------------------------------------
> 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]
>
>
--
Daniel Krisher
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
