[
https://issues.apache.org/jira/browse/MTOMCAT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Roger updated MTOMCAT-290:
----------------------------------
Description:
When using the tomcat7:run-war goal, the context is created based on the *path*
configuration parameter.
To use parallel deployment
(http://jagadesh4java.blogspot.be/2013/08/tomcat-7-parallel-deployment.html) I
usually append the timestamp to the path as shown below:
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat7-maven-plugin</artifactId>
<configuration>
<path>/myWar##${maven.build.timestamp}</path>
This works perfectly when deploying (tomcat7:deploy-only) the war since Tomcat
detect the ## and separate the context from the version.
However there the same process is not applied when running the war
(tomocat7:run-war) the *##* characters are URL encoded as *%13%13* and the
version (=timestamp) is in the resulting context.
Usually all character should be URL encoded as it is done as the moment, but
this case of parallel deployement might be an exception. (feature was
introducted in tomcat7).
was:
When using the tomcat7:run-war goal, the context is created based on the *path*
configuration parameter.
To use parallel deployment
(http://jagadesh4java.blogspot.be/2013/08/tomcat-7-parallel-deployment.html) I
usually append the timestamp to the path as shown below:
<groupId>org.apache.tomcat.maven</groupId>
<artifactId>tomcat7-maven-plugin</artifactId>
<configuration>
<path>/myWar##${maven.build.timestamp}</path>
This works perfectly when deploying (tomcat7:deploy-only) the war since Tomcat
detect the ## and separate the context from the version.
However there the same process is not applied when running the war
(tomocat7:run-war) the ## characters are URL encoded as %13%13 and the version
(=timestamp) is in the resulting context.
Usually all character should be URL encoded as it is done as the moment, but
this case of parallel deployement might be an exception. (feature was
introducted in tomcat7).
Priority: Minor (was: Major)
> Parallel deployment - Support version in war file name when using run-war goal
> ------------------------------------------------------------------------------
>
> Key: MTOMCAT-290
> URL: https://issues.apache.org/jira/browse/MTOMCAT-290
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: tomcat7
> Affects Versions: 2.2
> Environment: maven tomcat7
> Reporter: Olivier Roger
> Assignee: Olivier Lamy (*$^¨%`£)
> Priority: Minor
> Labels: maven, parallel-deployment, run-war
>
> When using the tomcat7:run-war goal, the context is created based on the
> *path* configuration parameter.
> To use parallel deployment
> (http://jagadesh4java.blogspot.be/2013/08/tomcat-7-parallel-deployment.html)
> I usually append the timestamp to the path as shown below:
> <groupId>org.apache.tomcat.maven</groupId>
> <artifactId>tomcat7-maven-plugin</artifactId>
> <configuration>
> <path>/myWar##${maven.build.timestamp}</path>
> This works perfectly when deploying (tomcat7:deploy-only) the war since
> Tomcat detect the ## and separate the context from the version.
> However there the same process is not applied when running the war
> (tomocat7:run-war) the *##* characters are URL encoded as *%13%13* and the
> version (=timestamp) is in the resulting context.
> Usually all character should be URL encoded as it is done as the moment, but
> this case of parallel deployement might be an exception. (feature was
> introducted in tomcat7).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
