Tapestry webapp locks files in WEB-INF/lib, preventing clean re-deploy without
restarting Tomcat.
-------------------------------------------------------------------------------------------------
Key: TAP5-704
URL: https://issues.apache.org/jira/browse/TAP5-704
Project: Tapestry 5
Issue Type: Bug
Components: quickstart, tapestry-core
Affects Versions: 5.1.0.5
Reporter: John Crim
Repro steps:
1. Run the Tapestry quickstart archetype (v 5.1.0.5)
2. Build it (mvn package) and deploy the WAR to the latest version of Tomcat
(6.0.18).
3. View the site in a browser (to start Tapestry)
4. Undeploy the webapp (either using /manager/html or an external command)
5. Rebuild the webapp and try to deploy it.
In short, this flaw adds significant time to each iteration during development.
And, if a developer doesn't understand that Tapestry webapps don't undeploy
properly, they can easily waste time with bugs that arise because old code is
still running in tomcat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
