Hi Adam, I just created a project using the archetype and live reloading works fine without tapestry.execution-mode=development.
Are you sure that you are in not in production mode? Your log should contain "5.3.7 (development mode)" next to the Tapestry logo. The CheckForUpdatesFilter should call ComponentTemplateSourceImpl.checkForUpdates() on a regular basis to detect template changes. Hope that helps. Felix 2015-03-18 15:38 GMT+01:00 Adam X <vbgnm3c...@gmail.com>: > Howdy, > > I'm returning to Tapestry after several years of inactivity and I'm > attempting a new project with T5.3.7. > > Ran a standard tut and found out that Live Class Reloading (following the > tutorial) does not work unless Eclipse RJR Run Config is amended with a JVM > param: -Dtapestry.execution-mode=development > > But, > > DevelopmentModule.java > > contains: > > // The factory default is true but during the early stages of an > // application > // overriding to false is a good idea. In addition, this is often > // overridden > // on the command line as -Dtapestry.production-mode=false > configuration.add(SymbolConstants.PRODUCTION_MODE, false); > > The Class Reloading page @ http://tapestry.apache.org/class-reloading.html > > Says the following: > > If Live Class Reloading doesn't workProduction Mode > > Starting with Tapestry 5.3, Live Class Reloading only works when not in > "Production Mode". Check your application module (usually AppModule.java) > to be sure you have: > configuration.add(SymbolConstants.PRODUCTION_MODE, "false"); > > and that this isn't being overridden to "true" on your application's > startup command line. > > All other issues such as automatic IDE build etc have been confirmed to be > setup properly. > > So this suggests that simply adding configuration with PRODUCTION_MODE > false should enable development mode and therefore live class reloading. > But that's not the case. A raw startup project setup according to > http://tapestry.apache.org/creating-the-skeleton-application.html , which > does have PRODUCTION_MODE false in DevelopmentMode.java and the run > configuration JVM parameter *empty* appears to run as if production mode = > true. > > Adam >
