It seems to be the same problem running the Jetty plugin in IntelliJ,
but a workaround if you edit the files inside IntelliJ is to
CTRL-s followed by CTRL-9
/Mats
On 2018-11-28 13:19, Qbyte Consulting wrote:
So it turns out IntelliJ doesn’t copy resources to the target folder. Gotta do
a mvn
So it turns out IntelliJ doesn’t copy resources to the target folder. Gotta do
a mvn compile.
Sent from my iPhone
> On 28 Nov 2018, at 15:34, Mats Andersson wrote:
>
> Usually tapestry.production-mode is used to check for updates less often so
> how can that help?
>
> Maybe tapestry.file-che
Yeah, sorry, I wasn't clear, the tapestry.production-mode should be FALSE
in development mode.
On Wed, Nov 28, 2018 at 11:34 AM Mats Andersson
wrote:
> Usually tapestry.production-mode is used to check for updates less often
> so how can that help?
>
> Maybe tapestry.file-check-interval is defin
Usually tapestry.production-mode is used to check for updates less often
so how can that help?
Maybe tapestry.file-check-interval is defined somewhere? Default is 1s
which should be enough in development. Also, make sure resources are
actually copied to the target directory when they are chang
Hi!
Make sure you have tapestry.production-mode=true set in one of your
tapestry modules, or set in the system properties section in your pom.xml.
Execution mode only specifies a list of additional tapestry modules
(usually just one) for runtime configuration.
On Wed, Nov 28, 2018 at 6:12 AM Qby
