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
debugging a deployed webapp 101
Hi, I heard that there is a way to get tomcat manager to dump the contents of the classpath loaders for a deployed application, but I haven't been able to find it. So far, I see only the ideas of using jstack or kill -3 (SIGQUIT) to dump the threads for the container process. Is there a way to get specific information about the loaded classpaths? tia, -Russ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: debugging a deployed webapp 101
Hey, that's pretty cool - nice that tomcat has full jmx interface now. By drilling down from the MBeans tab as you suggested, I can now see my classpath, but not the actual classes that are loaded. I do see a nice graph that tracks the total number of classes loaded, under the Classes tab. -Russ At 4:21 PM -0400 8/9/12, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Russ, On 8/9/12 3:46 PM, Russ Tremain wrote: I heard that there is a way to get tomcat manager to dump the contents of the classpath loaders for a deployed application, but I haven't been able to find it. So far, I see only the ideas of using jstack or kill -3 (SIGQUIT) to dump the threads for the container process. Do you want to get a thread dump, or do you want to get a list of JAR files that each ClassLoader is aware of? Is there a way to get specific information about the loaded classpaths? If you can attach to the process using jconsole, then you can look at the /Catalina/WebappClassLoader tree (somewhat predictably gives you details about WebappClassLoaders) and the /Catalina/Loader tree which has more information. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAkG9YACgkQ9CaO5/Lv0PCIJwCglZPb6a0AbAMt2ZEO43enPKiZ 8PoAn1sCtIoduMa5CRhtr7OuhFNSEzc8 =J2pm -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
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
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:
