Assemblies bundle files into an artifact, so they tend to belong in the "package" phase.
Eric On 3/6/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hello... Could the users of assembly plugin tell me to which phase of the lifecycle they bind the assembly plugin to? Also, how do I order the execution of plugins attached to the same phase in the scope of the current POM? Any help appreciated... Regards, /U -------------- Original message ---------------------- From: [EMAIL PROTECTED] > > I assumed that order of execution of plugins would be the order in which they > are > listed in the current POM and found out soon that that is a naive assumption (in > M2). > I also see that the problem exposes the complexity of Maven's POM inheritance > that its quite difficult to determine the order of execution of plugins from > ancestor/parent/current POMs. > > I have run into the problem in running the assembly plugin; I am creating a zip > assembly of my resources > and hence need to run resources:resources followed by assembly:attached in the > 'install' phase of > build lifecycle (pl see below). The parent/ancestor POM does not specify any > overrides for > either of the two plugins (resources or assembly). > > I see tha tth eproblem is described and solution suggested at > > > http://docs.codehaus.org/display/MAVEN/Suppression,+Ordering,+and+Replacement+of > +Plugins+and+Mojos+Bindings > > but do not see that Maven 2.0.4 has the "executionOrder" tags. > > To sum it up, when 'mvn install' is run, I need this POM to execute > resources:resources followed by > assembly:attached. What is the simplest way to accomplish this? > > Any hints greatly appreciated! > > Thanks, > > /U > > // Current POM > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-resources-plugin</artifactId> > <!-- > ! Make sure that that when 'mvn install' is run, resources > ! will be copied to the target directory for assembly plugin > ! (below) to act on. > !--> > <executions> > <execution> > <id>install-resources</id> <!-- this is used for inheritance merges > --> > <phase>install</phase> <!-- append to the packaging phase. --> > <goals> > <goal>resources</goal> <!-- goals == mojos --> > </goals> > </execution> > </executions> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-assembly-plugin</artifactId> > <configuration> > <descriptor>src/main/assembly/package.xml</descriptor> > </configuration> > > <!-- > ! Bind the assembly plugin to the install goal in the > ! build lifecycle. This implies that when 'mvn install' > ! is run, this zip assembly will be produced. > !--> > <executions> > <execution> > <id>make-assembly</id> <!-- this is used for inheritance merges --> > <phase>install</phase> <!-- append to the packaging phase. --> > <goals> > <goal>attached</goal> <!-- goals == mojos --> > </goals> > </execution> > </executions> > </plugin> > > --------------------------------------------------------------------- > 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]
-- Eric Redmond http://codehaus.org/~eredmond
