well a simpler way would be to bind an execution of the assembply plugin to the lifecycle (probably at the package phase) and then you would just go "mvn deploy" which will invoke all the plugins bound to phases on or before the "deploy" phase.
IIRC assembly:single the the preferred goal when binding to the lifecycle, so you would just add <executions> <execution> <id>some-id</id> <phase>package</phase> <goals><goal>single</goal></goals> </execution> </executions> to the <plugin> section for the assembly plugin On 21 March 2013 14:00, Zanzerkia, Robert <[email protected]> wrote: > Hi, > I have one plug-in that creates the zip file. > How do I change it to do deploy stage? > Normally I do mvn assembly:assembly deploy:deploy-file > > <plugin> > > <artifactId>maven-assembly-plugin</artifactId> > <version>2.4</version> > <configuration> > <descriptors> > > <descriptor>distribution.xml</descriptor> > </descriptors> > </configuration> > </plugin> > > Here is the distribution.xml > <assembly > xmlns=" > http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation=" > http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2 > http://maven.apache.org/xsd/assembly-1.1.2.xsd";> > <id>packages</id> > <formats> > <format>zip</format> > </formats> > > > <fileSets> > <fileSet> > <directory>./dist</directory> > <includes> > <include>**</include> > </includes> > <excludes> > <exclude>./target</exclude> > <exclude>./repository</exclude> > </excludes> > </fileSet> > </fileSets> > > </assembly> > > Thanks, > Robert > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf Of Baptiste > MATHUS > Sent: Thursday, March 21, 2013 9:40 AM > To: Maven Users List > Subject: Re: FW: Nexus deployment of a ZIP file... > > One simple way to go is to have a module dedicated to that assembly. > Then just mvn deploy it (or even simpler inside the whole multimodule > build). > > Cheers > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
