why are you trying to 'release' with the install plugin?
you should use the release plugin and bind the assembly and custom plugin to a
phase of the project lifecycle, its all very well documented all over the
place....
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2-beta-1</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>attached</goal>
</goals>
<configuration>
<descriptors>
<descriptor>src/main/assembly/aggregation.xml</descriptor>
</descriptors>
<outputDirectory>target/assembly</outputDirectory>
<workDirectory>target/assembly/work</workDirectory>
</configuration>
</execution>
</executions>
</plugin>
On Wed, 09 Jan 2008 09:19:44 nicolas de loof wrote:
> Hello,
>
> To release my project I need to call a rather complex maven command :
> "mvn install assembly:attached com.mycompany:myplugin:post-goal"
>
> I'd like to provide in my corporate POM some "macro command" to define
> custom goals / lifecycle phases to run such commands.
>
> example : "mvn release" to create the release.
>
> Is there any way to create such macro-commands with maven, when the
> standard lifecycle is not enough ? I don't thing so, but maybe some
> combination of profiles and invoker plugin could help ?
>
> Nico.
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
