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 changed in the
souce. This is needed to make Tapestry aware of changes.
/Mats
On 2018-11-28 09:09, Dmitry Gusev wrote:
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 Qbyte Consulting <qbyteconsult...@gmail.com>
wrote:
I’m finding resources are not dynamically reloading. Jetty config below,
what do I need to do?
<plugin>
<groupId>org.eclipse.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>9.2.0.M0</version>
<configuration>
<httpConnector>
<port>9095</port>
</httpConnector>
<systemProperties>
<systemProperty>
<name>tapestry.execution-mode</name>
<value>development</value>
</systemProperty>
<systemProperty>
<name>version</name>
<value>${project.version}</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
