Thanks. Completely forgot about that symbol.
On Wed, Jul 6, 2011 at 1:13 AM, Josh Canfield wrote:
> Can you just use tapestry.execution-mode ?
>
>
> http://tapestry.apache.org/configuration.html#Configuration-SettingExecutionModes
>
>String executionMode =
> System.getProperty("tapestry.e
I think Josh is on the right track ... that's essentially why
execution-mode was introduced. Often,. the execution mode drives the
production mode (i.e., a module loaded for "test" execution mode
provides the override for production mode to "false").
On Tue, Jul 5, 2011 at 4:13 PM, Josh Canfield
Can you just use tapestry.execution-mode ?
http://tapestry.apache.org/configuration.html#Configuration-SettingExecutionModes
String executionMode =
System.getProperty("tapestry.execution-mode", "production");
Currently TapestryFilter is only pulling it from system properties,
but the Sym
Currently a Tapestry app can run either in production mode or not production
mode (let's say test mode). Frequently this true/false decision is not
sufficient. For example, we have three different environments the
application is deployed to: test, integration and production. So a
three-value decisi
