[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    Re: Hot reloading and mvn:gae:run
From:       Nicolas Bouillon <nicolas () bouil ! org>
Date:       2010-11-25 9:22:56
Message-ID: AANLkTi=JDne579f5xTiMmfrwUUC+-2LRuVQ0Q1dX+B2V () mail ! gmail ! com
[Download RAW message or body]


To solve my issue, I've added a custom ant builder to Eclipse that copy the
target/classes folder to the target/myapp/WEB-INF/classes folder, and then
the tapestry hot reload of classes and resources works.

It works, but I have to trigger my custom builder manually with Ctrl-B
(build project), because it is not runned automatically.

On Mon, Nov 22, 2010 at 22:34, Nicolas Bouillon <nicolas@bouil.org> wrote:

> Hi,
>
> I use tapestry for more than one year now, and I'm very pleased with. I use
> it daily at work with mvn jetty:run and I much appreciate hot class
> reloading for pages and components.
>
> But at home I'm trying to use it to develop a Google App Engine
> Application, and I use the maven plugin net.kindleit:maven-gae-plugin with
> the target mvn gae:run.
>
> The hot reload is not working, because this plugin  doesn't work the same
> way as jetty:run : it assemble the war in a directory and run from there.
>
> Did anybody get the hot component reloading working in that configuration ?
>
> Thanks.
>
> Nicolas.
>
>


[prev in list] [next in list] [prev in thread] [next in thread]