Have the same Problem here with Tomcat 7.0.33 and Tapestry 5.3.6
Is it a tapestry problem or tomcat one? Any comments from devs?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Tomcat-7-Parallel-Deployment-tp5715717p5719909.html
Sent from the Tapestry - User mailing list
It does look like a similar problem but I don't think I'm doing anything
special. I'm not running clustered. All I did what change my Hudson build
script to add the build number into the warfile name and copy that to tomcat
webapps so I ended up with
CJIS##0645.war
which deployed as
CJIS##0645
I'
This bug seems to match with what you are seeing:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50679
Kalle
On Wed, Aug 22, 2012 at 8:21 AM, Kalle Korhonen
wrote:
> Cool that you found it. I was actually thinking that was off-topic
> here, so I only posted the following to Maven users list
Cool that you found it. I was actually thinking that was off-topic
here, so I only posted the following to Maven users list:
On Mon, Aug 20, 2012 at 11:16 AM, Kalle Korhonen
wrote:
> As a by-product of some infrastructure work some time ago I hacked
> together an Ant/Maven script for parallel depl
