Cargo-maven2-plugin插件自动部署

1、在settings.xml里面的pluginGroups节点增加org.codehaus.cargo以便命令行调用，然后增加server

2、部署到本地Web容器

If you wish to use Jetty 5.x, you don't have to specify  nor  in the  element because Jetty 5x is Cargo's default container.

2.1、standalone模式

在standalone模式，Cargo会从Web容器的安装目录复制一份配置(conf目录)到用户指定的目录，然后在此基础上部署应用，每次重新构建的时候，用户指定目录都会被清空，所有配置被重新生成。

                    org.codehaus.cargo
                    cargo-maven2-plugin
                    1.4.9
                    
                    
                        
                            tomcat7x

			    
                            E:\workspace\richinfo\apache-tomcat\apache-tomcat-7.0.65
                            ${project.build.directory}/cargo.log
                            
${project.build.directory}/output.log
                        
                        
                            standalone
                            ${project.build.directory}/tomcat7x
                            
                                
                                80
                            
                        
                    

mvn cargo:run启动

2.2、existing模式

在existing模式下，用户需要指定现有的web容器配置目录，然后Cargo会直接使用这些配置并将应用部署到其对应的位置。相当于替代人为部署到web容器中，即使web容器处于未运行状态。

                    org.codehaus.cargo
                    cargo-maven2-plugin
                    1.4.9

                    
                        
                            tomcat7x
                            E:\workspace\richinfo\apache-tomcat\apache-tomcat-7.0.65
                            ${project.build.directory}/cargo.log
                            
${project.build.directory}/output.log
                        
                        
                            existing
                            E:\workspace\richinfo\apache-tomcat\apache-tomcat-7.0.65
                        
                    

运行cargo:run之后在对应的tomcat的webapps目录下能够看到被部署的应用。

3、 部署到远程Web容器
注意在远程部署模式下， Container 元素的type子元素的值必须为remote，如果不指定，Cargo会默认使用installed，并寻找对应的容器安装目录或者安装包，一般我们远程部署的服务器上都有设定好的web容器了，并不需要再区安装。远程部署实现方式依靠web容器提供的管理部署功能。

3.1、在tomcat7的conf/tomcat-users.xml中增加角色和用户， 不然会报403，没法访问

3.2、配置pom.xml文件

 
                
                
                
                
                
                    org.codehaus.cargo
                    cargo-maven2-plugin
                    1.4.9  
                    
                        
                            tomcat7x
                            remote
                            ${project.build.directory}/cargo.log
                            
${project.build.directory}/output.log
                        
                        
                            runtime
                            
                                
                                http
                                9004
                                127.0.0.1
                                deploy
                                deploy
                            
                        
                        
                            
                                
                                
                                
                                
                                    
                                
                                
                                
                                
                                
                            
                        
                    
                    
                        
                            verify-deployer
                            package
                            
                                deployer-redeploy
                            
                        
                        
                            clean-deployer
                            clean
                            
                                deployer-undeploy
                            
                        
                    
                

Cargo插件中各个命令的之间的异同

Goals	Description
cargo:start	Start a container. That goal will: If the plugin configuration requires so, installs the container. If the plugin configuration defines a container with a standalone local configuration, it will create the configuration. If the plugin configuration contains one or more deployables, it will deploy these to the container automatically. If the plugin configuration contains no deployables but the project's packaging is Java EE (WAR, EAR, etc.), it will deploy the project's deployable to to the container automatically. And, of course, start the container. Note: A container that's started with cargo:start will automatically shut down as soon as the parent Maven instance quits (i.e., you see a BUILD SUCCESSFUL or BUILD FAILED message). If you want to start a container and perform manual testing, see our next goal cargo:run.
cargo:run	Start a container and wait for the user to press CTRL + C to stop. That goal will: If the plugin configuration requires so, installs the container. If the plugin configuration defines a container with a standalone local configuration, it will create the configuration. If the plugin configuration contains one or more deployables, it will deploy these to the container automatically. If the plugin configuration contains no deployables but the project's packaging is Java EE (WAR, EAR, etc.), it will deploy the project's deployable to to the container automatically. And, of course, start the container and wait for the user to press CTRL + C to stop.
cargo:stop	Stop a container.
cargo:restart	Stop and start again a container. If the container was not running before calling cargo:restart, it will simply be started.
cargo:configure	Create the configuration for a local container, without starting it. Note that the cargo:start and cargo:run goals will also install the container automatically (but will not call cargo:install).
cargo:package	Package the local container.
cargo:daemon-start	Start a container via the daemon. Read more on: Cargo Daemon Note: The daemon:start goal is actually equivalent to a restart in CARGO's terms; in the case a container with the same cargo.daemon.handleid already exists then it will be stopped first before your container is started. This also implies that in the case the new container fails to start, the old one will not be restarted.
cargo:daemon-stop	Stop a container via the daemon. Read more on: Cargo Daemon
cargo:deployer-deploy (aliased to cargo:deploy)	Deploy a deployable to a running container. Note: The cargo:start and cargo:run do already deploy the deployables specified in the configuration to the container; as a result calling cargo:deploy for a container which has been started by CARGO in the same Maven2/Maven3 project will most likely cause a second deployment of the same deployables (and might even fail).
cargo:deployer-undeploy(aliased to cargo:undeploy)	Undeploy a deployable from a running container.
cargo:deployer-start	Start a deployable already installed in a running container.
cargo:deployer-stop	Stop a deployed deployable without undeploying it.
cargo:deployer-redeploy(aliased to cargo:redeploy)	Undeploy and deploy again a deployable. If the deployable was not deployed before calling cargo:deployer-redeploy (or its alias cargo:redeploy) it will simply be deployed.
cargo:uberwar	Merge several WAR files into one.
cargo:install	Installs a container distribution on the file system. Note that the cargo:start goal will also install the container automatically (but will not call cargo:install).
cargo:help	Get help (list of available goals, available options, etc.).

从上面可以看出，cargo:start于cargo:run的不同之处了吧？cargo:start的生命周期依赖于maven实例的生命周期，也就是说，maven构建成功或者失败之后，cargo插件的生命周期也自动停止了；而cargo:run不同，不管maven是否构建成功或者失败，都必须手工去按Ctrl + C来停止。

参考资料：

1.徐文斌的《Maven实战》

2.http://cargo.codehaus.org/Maven2+Plugin+Reference+Guide

3.http://cargo.codehaus.org/Maven2+plugin

4.http://cargo.codehaus.org/Deploying+to+a+running+container

5.https://codehaus-cargo.github.io/cargo/Starting+and+stopping+a+container.html