Re: confused by tomcat6/7 docs
At 10:50 AM +0200 7/9/12, Olivier Lamy wrote:
Hi,
2012/7/8 Russ Tremain ru...@releasetools.org:
ahh... thanks. bad assumption on my part that tomcat7-maven was a superset.
what would really be cool is an incremental deploy, but not sure if the
tomcat remote deploy api supports that or not.
with incremental you mean for classes too ? or for jsp,css, jss etc.. ?
sorry I missed your reply.
I was thinking anything that had changed in the war from the previous
deployment.
sort of an rsync type functionality.
just an idea..
/r
meantime I will see if we can revert to tomcat6-maven plugin to see if we
can speed the build/deploy development cycle up.
thx,
/r
At 10:16 PM +0200 7/7/12, Olivier Lamy wrote:
Yup because currently not all goals from tomcat6 have been implemented
in tomcat7.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
whereas.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
You can load an issue (if possible with a patch :-) ) for goals you'd like
see.
2012/7/6 Russ Tremain ru...@releasetools.org:
Hi Oliver,
I must say I'm a bit confused by the examples docs for
tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist. The
reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an exploded
war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a
method
to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:deploy-only
Description: Deploy a WAR to Tomcat witjout forking the package lifecycle
Implementation:
org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployOnlyMojo
Language: java
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,
RE: confused by tomcat6/7 docs
Russ-
Can you take the mode configuration attribute from
org.apache.tomcat.maven:tomcat7 plugin and modify the plugin code to deploy
*only what you want*
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.Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
Date: Thu, 9 Aug 2012 12:39:11 -0700
To: users@tomcat.apache.org
From: ru...@releasetools.org
Subject: Re: confused by tomcat6/7 docs
CC: users@tomcat.apache.org
At 10:50 AM +0200 7/9/12, Olivier Lamy wrote:
Hi,
2012/7/8 Russ Tremain ru...@releasetools.org:
ahh... thanks. bad assumption on my part that tomcat7-maven was a
superset.
what would really be cool is an incremental deploy, but not sure if the
tomcat remote deploy api supports that or not.
with incremental you mean for classes too ? or for jsp,css, jss etc.. ?
sorry I missed your reply.
I was thinking anything that had changed in the war from the previous
deployment.
sort of an rsync type functionality.
just an idea..
/r
meantime I will see if we can revert to tomcat6-maven plugin to see if we
can speed the build/deploy development cycle up.
thx,
/r
At 10:16 PM +0200 7/7/12, Olivier Lamy wrote:
Yup because currently not all goals from tomcat6 have been implemented
in tomcat7.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
whereas.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
You can load an issue (if possible with a patch :-) ) for goals you'd like
see.
2012/7/6 Russ Tremain ru...@releasetools.org:
Hi Oliver,
I must say I'm a bit confused by the examples docs for
tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist. The
reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an exploded
war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a
method
to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation:
org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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
Re: confused by tomcat6/7 docs
Hi,
2012/7/8 Russ Tremain ru...@releasetools.org:
ahh... thanks. bad assumption on my part that tomcat7-maven was a superset.
what would really be cool is an incremental deploy, but not sure if the
tomcat remote deploy api supports that or not.
with incremental you mean for classes too ? or for jsp,css, jss etc.. ?
meantime I will see if we can revert to tomcat6-maven plugin to see if we can
speed the build/deploy development cycle up.
thx,
/r
At 10:16 PM +0200 7/7/12, Olivier Lamy wrote:
Yup because currently not all goals from tomcat6 have been implemented
in tomcat7.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
whereas.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
You can load an issue (if possible with a patch :-) ) for goals you'd like
see.
2012/7/6 Russ Tremain ru...@releasetools.org:
Hi Oliver,
I must say I'm a bit confused by the examples docs for
tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist. The
reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an exploded
war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a method
to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:deploy-only
Description: Deploy a WAR to Tomcat witjout forking the package lifecycle
Implementation:
org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployOnlyMojo
Language: java
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
Re: confused by tomcat6/7 docs
ahh... thanks. bad assumption on my part that tomcat7-maven was a superset.
what would really be cool is an incremental deploy, but not sure if the
tomcat remote deploy api supports that or not.
meantime I will see if we can revert to tomcat6-maven plugin to see if we can
speed the build/deploy development cycle up.
thx,
/r
At 10:16 PM +0200 7/7/12, Olivier Lamy wrote:
Yup because currently not all goals from tomcat6 have been implemented
in tomcat7.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
whereas.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
You can load an issue (if possible with a patch :-) ) for goals you'd like see.
2012/7/6 Russ Tremain ru...@releasetools.org:
Hi Oliver,
I must say I'm a bit confused by the examples docs for
tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist. The
reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an exploded
war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a method
to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:deploy-only
Description: Deploy a WAR to Tomcat witjout forking the package lifecycle
Implementation:
org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployOnlyMojo
Language: java
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/html)
The full URL of the Tomcat manager instance to use.
Re: confused by tomcat6/7 docs
Yup because currently not all goals from tomcat6 have been implemented
in tomcat7.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat6-maven-plugin/plugin-info.html
whereas.
http://tomcat.apache.org/maven-plugin-2.0-SNAPSHOT/tomcat7-maven-plugin/plugin-info.html
You can load an issue (if possible with a patch :-) ) for goals you'd like see.
2012/7/6 Russ Tremain ru...@releasetools.org:
Hi Oliver,
I must say I'm a bit confused by the examples docs for
tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist. The
reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an exploded
war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a method
to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull
help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:deploy-only
Description: Deploy a WAR to Tomcat witjout forking the package lifecycle
Implementation:
org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployOnlyMojo
Language: java
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:exec-war
Description: (no description available)
Implementation: org.apache.tomcat.maven.plugin.tomcat7.run.ExecWarMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
Available parameters:
confused by tomcat6/7 docs
Hi Oliver,
I must say I'm a bit confused by the examples docs for tomcat7-maven-plugin.
I see reference to a war:explode goal, which doesn't seem to exist.
The reference is here:
http://tomcat.apache.org/maven-plugin-2.0-beta-1/context-goals.html
But when I dump the plugin documentation [1], I see no such goal.
What I would like to find out about the possibility to deploy an
exploded war image to a local tomcat instance.
I've been successfully using the deploy (tomcat7:deploy) goal, but my
developers are complaining that it is too slow. I need to work out a
method to use an exploded war.
Any help appreciated...
thanks!
-Russ
[1] mvn -Dplugin=tomcat7 -DgroupId=org.apache.tomcat.maven -Dfull help:describe
...
[INFO] org.apache.tomcat.maven:tomcat7-maven-plugin:2.0-beta-1
Name: Apache Tomcat Maven Plugin :: Tomcat 7.x
Description: The Tomcat Maven Plugin provides goals to manipulate WAR
projects within the Tomcat 7.x servlet container.
Group Id: org.apache.tomcat.maven
Artifact Id: tomcat7-maven-plugin
Version: 2.0-beta-1
Goal Prefix: tomcat7
This plugin has 8 goals:
tomcat7:deploy
Description: Deploy a WAR to Tomcat.
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:deploy-only
Description: Deploy a WAR to Tomcat witjout forking the package lifecycle
Implementation: org.apache.tomcat.maven.plugin.tomcat7.deploy.DeployOnlyMojo
Language: java
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/html)
The full URL of the Tomcat manager instance to use.
username
The tomcat username to use for deployment
warFile
The path of the WAR file to deploy.
tomcat7:exec-war
Description: (no description available)
Implementation: org.apache.tomcat.maven.plugin.tomcat7.run.ExecWarMojo
Language: java
Before this mojo executes, it will call:
Phase: 'package'
Available parameters:
accessLogValveFormat (Default: %h %l %u %t )
see http://tomcat.apache.org/tomcat-7.0-doc/config/valve.html
attachArtifact (Default: true)
Attach or not the generated artifact to the build (use true if you want
to install or deploy it)
attachArtifactClassifier (Default: exec-war)
the classifier to use for the attached/generated artifact
attachArtifactClassifierType (Default: jar)
the type to use for the attached/generated artifact
buildDirectory (Default:
