Recently I was developing a and after doing the build, I used to copy the generated WAR file to Tomcat webapps directory. It was time-consuming, boring and sometimes I used to miss the updated WAR file to copy and notice it later on.
4.0.0 MyWebapp MyWebapp 0.0.1-SNAPSHOT war /Users/pankaj/Dev_Softwares/apache-tomcat-7.0.32/webapps src maven-war-plugin 2.3 WebContent false maven-compiler-plugin 3.1 1.7 1.7 maven-antrun-plugin integration-test run ${project.artifactId}
The change was really simple, create a property to define the tomcat deploy directory and add finalName configuration to skip version details from the WAR file.
mvn clean package – It will just build the project, will not try to deploy it into tomcat container.
mvn clean package –它只会构建项目，不会尝试将其部署到tomcat容器中。
Above approach solved my problem, but there were two shortcomings;
上面的方法解决了我的问题，但是有两个缺点。
Since tomcat deploy folder is hardcoded in the pom.xml, if I change tomcat server location then I would have to change it here too. Also because it’s my user configuration, I can’t check in this code into repository. 由于tomcat deploy文件夹是硬编码在pom.xml中的，因此，如果我更改了tomcat服务器位置，则也必须在此处进行更改。 另外，由于这是我的用户配置，因此无法将此代码检入到存储库中。
I can’t use this approach to deploy the application into any remote server. 我无法使用这种方法将应用程序部署到任何远程服务器中。
Tomcat7 Maven插件 (Tomcat7 Maven Plugin)
Because of above shortcomings, I looked online for better solutions and found that there is a plugin already for this job – .
由于上述缺点，我在网上寻找更好的解决方案，并发现已经有一个用于此工作的 。
We can use this plugin with some configuration settings to deploy our application into Tomcat server using their management console API.
Before we can use Apache Tomcat Maven Plugin, we need to perform some configuration settings. Let’s look at these configurations one by one. Note that I am using Tomcat-7, if you are using any other version then some configurations might need to be changed accordingly.
Adding Manager Roles and User in Tomcat 7: We need to add manager-gui and manager-script roles in tomcat-users.xml file and create a user with these roles. Just add below lines to your tomcat-users.xml file and restart the server.
Maven Project pom.xml changes: Final step is to configure Tomcat Maven Plugin in the web application pom.xml file. Just add below lines to your pom.xml plugins section.
Below is the sample output produced by the deploy command for tomcat7-maven-plugin.
以下是deploy命令为tomcat7-maven-plugin生成的示例输出。
pankaj:MyWebapp pankaj$ mvn tomcat7:deploy[INFO] Scanning for projects...[INFO] [INFO] ------------------------------------------------------------------------[INFO] Building MyWebapp 0.0.1-SNAPSHOT[INFO] ------------------------------------------------------------------------[INFO] [INFO] >>> tomcat7-maven-plugin:2.2:deploy (default-cli) @ MyWebapp >>>[INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ MyWebapp ---[debug] execute contextualize[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent![INFO] skip non existing resourceDirectory /Users/pankaj/Documents/workspace/j2ee/MyWebapp/src/main/resources[INFO] [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ MyWebapp ---[INFO] Nothing to compile - all classes are up to date[INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ MyWebapp ---[debug] execute contextualize[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent![INFO] skip non existing resourceDirectory /Users/pankaj/Documents/workspace/j2ee/MyWebapp/src/test/resources[INFO] [INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ MyWebapp ---[INFO] No sources to compile[INFO] [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ MyWebapp ---[INFO] No tests to run.[INFO] Surefire report directory: /Users/pankaj/Documents/workspace/j2ee/MyWebapp/target/surefire-reports------------------------------------------------------- T E S T S-------------------------------------------------------Results :Tests run: 0, Failures: 0, Errors: 0, Skipped: 0[INFO] [INFO] --- maven-war-plugin:2.3:war (default-war) @ MyWebapp ---[INFO] Packaging webapp[INFO] Assembling webapp [MyWebapp] in [/Users/pankaj/Documents/workspace/j2ee/MyWebapp/target/MyWebapp-0.0.1-SNAPSHOT][INFO] Processing war project[INFO] Copying webapp resources [/Users/pankaj/Documents/workspace/j2ee/MyWebapp/WebContent][INFO] Webapp assembled in [26 msecs][INFO] Building war: /Users/pankaj/Documents/workspace/j2ee/MyWebapp/target/MyWebapp-0.0.1-SNAPSHOT.war[INFO] [INFO] <<< tomcat7-maven-plugin:2.2:deploy (default-cli) @ MyWebapp <<<[INFO] [INFO] --- tomcat7-maven-plugin:2.2:deploy (default-cli) @ MyWebapp ---[INFO] Deploying war to https://localhost:9090/MyWebapp SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".SLF4J: Defaulting to no-operation (NOP) logger implementationSLF4J: See https://www.slf4j.org/codes.html#StaticLoggerBinder for further details.Uploading: https://localhost:9090/manager/text/deploy?path=%2FMyWebappUploaded: https://localhost:9090/manager/text/deploy?path=%2FMyWebapp (2 KB)[INFO] tomcatManager status code:200, ReasonPhrase:OK[INFO] OK - Deployed application at context path /MyWebapp[INFO] ------------------------------------------------------------------------[INFO] BUILD SUCCESS[INFO] ------------------------------------------------------------------------[INFO] Total time: 3.185s[INFO] Finished at: Mon Sep 15 18:07:00 IST 2014[INFO] Final Memory: 13M/159M[INFO] ------------------------------------------------------------------------
You can go to your Tomcat Manager App and confirm that application is deployed or you can directly access the application in the browser to confirm it. That’s all for tomcat maven plugin and tomcat7-maven-plugin example.