We usually simply set -Dtapestry.production-mode=false in the JVM when we want dev mode.
On Tue, Aug 25, 2015 at 1:51 PM, Poggenpohl, Daniel < daniel.poggenp...@isst.fraunhofer.de> wrote: > Hi everyone, > > it seems that production mode (is set to true) is the problem. > > We use build profiles and have three stages: > 1. Local development > 2. Deploying to a Test VM for load tests > 3. Deploying to the official VM > > Our tapestry module POM reflects this. > When I add a property > <tapestry.execution-mode>development</tapestry.execution-mode> > to the POM, it should load the additional DevelopmentModule which sets the > production mode to false. > The DevelopmentModule isn't loaded, though. > > Isn't this the way to go? > > Regards, > Daniel P. > > -----Ursprüngliche Nachricht----- > Von: Stephen Nutbrown [mailto:steves...@gmail.com] > Gesendet: Dienstag, 25. August 2015 13:26 > An: Tapestry users > Betreff: Re: Debugging Tapestry with IntelliJ IDEA > > Just to confirm it also works fine here too. I've found IntelliJ to be > absolutely fantastic so far. I'm running it using jetty but I know there is > an option for tomcat... I don't know if that could make a difference? > On 25 Aug 2015 11:33 am, "Chris Poulsen" <mailingl...@nesluop.dk> wrote: > > > It works fine with IDEA here. A possibility could be that you are > > running in production mode? > > > > On Tue, Aug 25, 2015 at 12:04 PM, Poggenpohl, Daniel < > > daniel.poggenp...@isst.fraunhofer.de> wrote: > > > > > Hello everyone, > > > > > > we are evaluating IntelliJ IDEA for development and so far it has > > > been quite good. > > > But the Tapestry specifics seem to hinder further evaluation. > > > Does anyone here use IntelliJ for development? > > > > > > When we debug code, page properties are always seen as having a "null" > > > value instead of the proxy that Eclipse used to show. What are we > > > doing wrong? > > > > > > Regards, > > > Daniel P. > > > > > >
