Btw, your solution didn't work for me (activating based on a property set in another module). It seems that the profiles are being parsed before the property is set in my module.
2009/5/12 Bocalinda <[email protected]> > Hi Jesse, > > As a workaround for the profile activation by packaging type, it may be an > option to use: > > <activation> > <property> > <name>${project.packaging}</name> > <value>war</value> > </property> > </activation> > > Cheers, > > Pieter > > 2009/5/11 <[email protected]> > >> Hi Pieter, >> >> >> On Mon, May 11, 2009 at 11:47 AM, Bocalinda <[email protected]> wrote: >> > >> > What exactly do you mean by "attachment to a life cycle phase"? >> > You mean like this: >> > >> > <executions> >> > <execution> >> > <id>start-container</id> >> > <phase>pre-integration-test</phase> >> > <goals> >> > <goal>start</goal> >> > <goal>deploy</goal> >> > </goals> >> > </execution> >> > <execution> >> > <id>stop-container</id> >> > <phase>post-integration-test</phase> >> > <goals> >> > <goal>stop</goal> >> > </goals> >> > </execution> >> > </executions> >> > >> >> Yes, that's exactly right. Inside a profile in your super pom.xml. >> -jesse >> >> -- >> There are 10 types of people in this world, those >> that can read binary and those that can not. >> > >
