> Is there a parent project that will insist in deploying resources to a > Tomcat project? I am currently doing:
Google tells me there are a few tomcat plugins for Maven. http://mojo.codehaus.org/tomcat-maven-plugin/ http://cargo.codehaus.org/ (read more: http://www.gorerle.com/vlab-wiki/index.php?title=Tomcat_Deployment_in_Maven2) > mvn -o jar:jar; cp target/CreateOrCommentHandler-0.0.1-SNAPSHOT.jar > ~/tomcat/webapps/myapp/WEB-INF/lib/ Any particular reason why you're invoking jar:jar rather than simply "mvn package", or even better, "mvn clean package"? > Finally, I noticed there was a way to get a list of targets in maven1 - > does this switch exist in maven2? The concept of a "list of targets" is not appropriate for Maven2, as it is for ant and m1. You should be binding plugins to the build lifecycle so every build automatically uses the various plugins it requires at the proper time during the lifecycle of your build. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
