Ah. What you have done is bound plugin executions to the Maven build lifecycle. But the way you execute things you're executing the plugin directly. Due to how you've configured the plugin executions in the pom (not using pluginManagement) this is not applied when calling the plugin directly.
So with your current setup, calling mvn pre-integration-test should work as it will perform a lifecycle build. Or, which I think is a more suitable solution to what you want to do, is to configure the plugin through pluginManagement and then call the plugin directly. But as you want to deploy several artifacts I'm not sure that the latter suggestion would work with the plugin your using. You need to check the documentation. If it doesn't work, I think that you could use the Cargo plugin as it supports multiple deployables through one single configuration. /Anders PS. I just now noticed that this was sent to the dev list. You should move the thread to the users list as the dev list is for maven development questions. On Tue, Aug 30, 2011 at 17:33, peekay_21 <[email protected]> wrote: > I am executing: > mvn tomcat:deploy > > For clarification "pom packaging" is simply an empty project with just the > .project file and pom.xml, is that what your referring to? > If so I have done that and the result was the same. > is there some other maven distinction for "pom packaging"? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Multiple-WAR-deploy-with-maven-to-tomcat-tp4750066p4750462.html > Sent from the Maven Developers mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > 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]
