Apache Tomcat Maven Plugin 参数大全(Tomcat 6)

tomcat6:deploy/deploy-only/redeploy/exploded/inplace
  1.Deploy a WAR to Tomcat.

2.Deploy a WAR to Tomcat witjout forking the package lifecycle

3.Redeploy a WAR in Tomcat. Deploy with forcing update flag to true

4.Deploy an exploded WAR to Tomcat.

5.Deploy a WAR in-place to Tomcat.

Available parameters:

charset (Default: ISO-8859-1)
      The URL encoding charset to use when communicating with Tomcat manager.

contextFile

The path of the Tomcat context XML file. This is not used for war
      deployment mode.

ignorePackaging (Default: false)
      If set to true ignore if packaging of project is not ‘war‘.

mode (Default: war)
      The deployment mode to use. This must be either war to deploy the war,
      context to deploy the context XML file, or both to deploy the war with the
      context XML file.

password
      The password to use for deployment

path (Default: /${project.artifactId})默认为项目名
      The webapp context path to use for the web application being run. This
      must always start with a forward-slash (‘/‘).

server
      The server id in settings.xml to use when authenticating with Tomcat
      manager, or null to use defaults of username admin and no password.

tag
      The Tomcat webapp tag name to use.

update (Default: false)
      Whether Tomcat should automatically undeploy webapps that already exist
      when deploying.

url (Default: http://localhost:8080/manager)
      The full URL of the Tomcat manager instance to use.

username
      The tomcat username to use for deployment

warFile/warFile/warFile/warDirectory/warDirectory
      The path of the WAR file to deploy.

tomcat6:run/run-war/run-war-only
  1.Runs the current project as a dynamic web application using an embedded Tomcat
  server.

2.Runs the current project as a packaged web application using an embedded
Tomcat server.

3.Runs the current project as a packaged web application using an embedded
Tomcat server without forking the package cycle.

Available parameters:

addContextWarDependencies (Default: false)
      Will create a tomcat context for each dependencies of war type. To
      preserve backward compatibility it‘s false by default.

additionalConfigFilesDir (Default: ${basedir}/src/main/tomcatconf)
      The directory contains additional configuration Files that copied in the
      Tomcat conf Directory.

classesDir/无/无
      The classes directory for the web application being run.

configurationDir
      The directory to create the Tomcat server configuration under.

contextFile
      The path of the Tomcat context XML file.

delegate (Default: true)/无/无
      Set the ‘follow standard delegation model‘ flag used to configure our
      ClassLoader.

fork (Default: false)
      Set this to true to allow Maven to continue to execute after invoking the
      run goal.

httpsPort (Default: 0)
      The https port to run the Tomcat server on. By default it‘s 0 this means
      won‘t be started. The https connector will be started only for value > 0.

ignorePackaging (Default: false)
      If set to true ignore if packaging of project is not ‘war‘.

keystoreFile
      Override the default keystoreFile for the HTTPS connector (if enabled)

keystorePass
      Override the default keystorePass for the HTTPS connector (if enabled)

path (Default: /${project.artifactId})
      The webapp context path to use for the web application being run. This
      must always start with a forward-slash (‘/‘).

pluginArtifacts
      (no description available)

port (Default: 8080)
      The port to run the Tomcat server on.

serverXml
      server.xml to use Note if you use this you must configure in this file
      your webapp paths.

systemProperties
      List of System properties to pass to the Tomcat Server.

tomcatWebXml
      overriding the providing web.xml to run tomcat

uriEncoding (Default: ISO-8859-1)
      The character encoding to use for decoding URIs.

useSeparateTomcatClassLoader (Default: false)
      if true a new classLoader separated from maven core will be created to
      start tomcat.

warSourceDirectory/warDirectory/warDirectory
      The web resources directory for the web application being run.

tomcat6:reload
  Reload a WAR in Tomcat.

Available parameters:

charset (Default: ISO-8859-1)
      The URL encoding charset to use when communicating with Tomcat manager.

ignorePackaging (Default: false)
      If set to true ignore if packaging of project is not ‘war‘.

password
      The password to use for deployment

path (Default: /${project.artifactId})
      The webapp context path to use for the web application being run. This
      must always start with a forward-slash (‘/‘).

server
      The server id in settings.xml to use when authenticating with Tomcat
      manager, or null to use defaults of username admin and no password.

url (Default: http://localhost:8080/manager)
      The full URL of the Tomcat manager instance to use.

username
      The tomcat username to use for deployment

tomcat6:resources/   info/list/roles/    sessions/start/stop/   undeploy

1.Lists JNDI resources in Tomcat.

2.Lists information about the Tomcat version, OS, and JVM properties.

3.Lists all the currently deployed web applications in Tomcat.

4.Lists security roles in Tomcat.

5.Lists session information for a WAR in Tomcat.

Available parameters:

charset (Default: ISO-8859-1)
      The URL encoding charset to use when communicating with Tomcat manager.

password
      The password to use for deployment

path (Default: /${project.artifactId})
      The webapp context path to use for the web application being run. This
      must always start with a forward-slash (‘/‘).

server
      The server id in settings.xml to use when authenticating with Tomcat
      manager, or null to use defaults of username admin and no password.

url (Default: http://localhost:8080/manager)
      The full URL of the Tomcat manager instance to use.

username
      The tomcat username to use for deployment.

type/后面都无
      The class name of the resources to list, or null for all.

无/无/无/无/后4个有 ignorePackaging (Default: false)
      If set to true ignore if packaging of project is not ‘war‘.

最后1个有 failOnError (Default: true)
      Whether to fail the build if the web application cannot be undeployed.

tomcat6:shutdown
  Shuts down all possibly started embedded tomcat servers. This will be
  automatically down through a shutdown hook or you may call this Mojo to shut
  them down explictly.

By default the shutdown goal is not bound to any phase. For integration tests
  you might want to bind it to post-integration-test.

Available parameters:

path (Default: /${project.artifactId})
      The webapp context path to use for the web application being run. This
      must always start with a forward-slash (‘/‘).

时间: 2024-10-06 20:04:29

Apache Tomcat Maven Plugin 参数大全(Tomcat 6)的相关文章

Tomcat Maven Plugin部署Maven Web应用

Tomcat官方提供了Maven插件用于部署基于Maven的Web应用,不同版本Tomcat使用的插件不同,不同版本插件的使用也有一定区别,详细信息可参考http://tomcat.apache.org/maven-plugin.html.下面记录的是我在Eclipse环境中使用Tomcat Maven Plugin-2.2在Tomcat7中部署Maven Web应用的配置过程: 第一步:配置Tomcat manager用户: 打开Tomcat根目录下conf目录中的tomcat_user.xm

Tomcat Maven Plugin使用

原文同步至:http://www.waylau.com/tomcat-maven-plugin/ Apache Tomcat 的 Maven 插件提供了 goal,实现将 Apache Tomcat servlet 容器整合进 WAR 项目.你可以通过 Apache Maven 运行 WAR 项目而无需部署 WAR 文件到 Apache Tomcat 的实例. 详见下面网站: Trunk (开发环境下) Version 2.2 (2013-11-11) Version 2.1 (2013-02-

Apache Tomcat Maven Plugin

groupId and Mojo name change Since version 2.0-beta-1 tomcat mojos has been renamed to tomcat6 and tomcat7 with the same goals. You must configure your pom to use this new groupId: <pluginManagement> <plugins> <plugin> <groupId>org

tomcat maven plugin热部署

首先启动tomcat,然后在tomcat的tomcat-users.xml配置文件里写入: <role rolename="tomcat"/> <role rolename="manager-gui"/> <role rolename="manager-script"/> <user username="tomcat" password="tomcat" roles

【Tomcat】Tomcat配置JVM参数步骤

这里向大家描述一下如何使用Tomcat配置JVM参数,Tomcat本身不能直接在计算机上运行,需要依赖于硬件基础之上的操作系统和一个java虚拟机.您可以选择自己的需要选择不同的操作系统和对应的JDK的版本,但还是推荐您使用Sun公司发布的JDK. Tomcat配置JVM参数 Tomcat本身不能直接在计算机上运行,需要依赖于硬件基础之上的操作系统和一个java虚拟机.您可以选择自己的需要选择不同的操作系统和对应的 JDK的版本(只要是符合Sun发布的Java规范的),但我们推荐您使用Sun公司

maven plugin在tomcat 热部署

前言: 此处的方法适用于tomcat6 和 tomcat7,对于最新的tomcat8还没有进行过测试,有兴趣的同学可以自己测一下. 总共分为五步: 1.在tomcat中配置用户权限,即添加管理员帐号 2.在maven中添加server,配置tomcat的管理员帐号密码 3.在project中添加插件,以及maven中配置的server, 4.设置部署命令 5.进行部署 下面进行分步骤讲解: 一. 在tomcat中配置用户权限,即添加管理员帐号. 我们需要实现热部署,自然就需要通过maven操作t

idea 使用maven plugin tomcat 运行正常,无法进入debug模式

idea版本:2017.3.1 .在pom.xml引入plugin tomcat,如下: <build> <defaultGoal>install</defaultGoal> <plugins> <plugin> <groupId>org.apache.tomcat.maven</groupId> <artifactId>tomcat7-maven-plugin</artifactId> <v

有关使用Maven常见问题总结(Eclipse中使用Maven、Maven项目部署到tomcat等问题)

最近一些项目需要让Maven来管理,一种情况是将之前的eclipse的Java Project项目和Web project 加入Maven管理,还有一种情况是,将SVN上的Maven项目拉到本地,在eclipse中使用时遇到的一些棘手问题,问题过程和解决具体方案如下: 1.在eclipse中安装maven插件后启动eclipse时,会遇到如下警告: The Maven Integration requires that Eclipse be running in a JDK, because a

java学习---maven工程的创建+tomcat的热部署

 一.创建maven工程 1.创建maven的的web功能 2.在创建完成后,可能发现功能有错误,在eclipse中的错误描述如下: The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path 解决办法如下: 步骤:bulid Path --> Configure Bulid Path --> Libraries --> add Library -->