On Tue, 15 Jun 2010 19:45:35 -0300, Paul Stanton <p...@mapshed.com.au>
wrote:
http://tapestry.apache.org/tapestry5.1/guide/reload.html*
*Hi all,
Hi!
I've our project is set up so that tomcat runs from the src/main/webapp
dir which contains jars and compiled code. Maven is set up to maintains
the jars within src/main/webapp/WEB-INF/lib and src/main/java and
src/main/resources compile to /src/main/webapp/WEB-INF/classes.
I'm aware that this is not quite the typical setup.
Why not Jetty, at least when developing?
Quite often a change to a resource such as a TML or a JS referenced by
an @IncludeJavascript will cause a compile error if the web app is
running:
...The project was not built due to "Could not delete
'.../src/main/webapp/WEB-INF/classes/com'...
and any change to a tapestry page or component fails to hot-replace.
I've seen this problem happening with Jetty too, but only on Windows. This
is a problem of file locking, not Tapestry itself or your setup. I use
Linux and I've never met this problem. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
